• Re: Bug#1060099: telegram-desktop: FTBFS on mips64el: ./obj-mips64el-li

    From Nicholas Guriev@21:1/5 to Sebastian Ramacher on Sat Jan 6 21:04:22 2024
    To: 1060099@bugs.debian.org

    Hello!

    On 06.01.2024 00:09:14 MSK you wrote:
    CMakeFiles/td_scheme.dir/gen/scheme.cpp.o: in function `MTPDchannel::read(int const*&, int const*)':
    ./obj-mips64el-linux-gnuabi64/Telegram/./obj-mips64el-linux-gnuabi64/Telegram/gen/scheme.cpp:16435:(.text+0x1600a0): relocation truncated to fit: R_MIPS_GOT_PAGE against `.text'
    CMakeFiles/td_scheme.dir/gen/scheme.cpp.o: in function `MTPDuser::read(int const*&, int const*)':
    ./obj-mips64el-linux-gnuabi64/Telegram/./obj-mips64el-linux-gnuabi64/Telegram/gen/scheme.cpp:15827:(.text+0x16139c): relocation truncated to fit: R_MIPS_GOT_PAGE against `.text'
    collect2: error: ld returned 1 exit status

    Sorry, I have no idea how to properly fix this linker error. The aforementioned translation unit already uses compiler flags -mxgot -fPIC. They helped before. It seems the scheme.cpp has reached the limit of code size of single TU.

    Primary platform for Telegram Desktop is amd64; arm64 is also somewhat popular. This issue is platform specific. And I daresay it is not that serious to block release on unaffected architectures.

    -----BEGIN PGP SIGNATURE-----

    iHUEABYIAB0WIQQRm7llN8yxifaG60cF2qh9JI3wlQUCZZmWJgAKCRAF2qh9JI3w ld6oAQCv5eSfkWt1UTsXnmk23bjsAqvqlkCwm+xGiVT7OBHtRQD/ZbSzNstMmivn LjFH4mbKdHOBTe3FphCne9uYyHfekQI=
    =3Ros
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)