depends: Cross-compiling qt for arm-linux-gnueabihf fails #29980

1. 
   hebasto commented at 5:40 pm on April 27, 2024: member

   On Ubuntu 24.04 with glibc 2.39:

   0compiling ../3rdparty/zlib/src/gzclose.c
   1In file included from /usr/arm-linux-gnueabihf/include/features.h:394,
   2                 from /usr/arm-linux-gnueabihf/include/bits/libc-header-start.h:33,
   3                 from /usr/arm-linux-gnueabihf/include/stdio.h:28,
   4                 from ../3rdparty/zlib/src/gzguts.h:40,
   5                 from ../3rdparty/zlib/src/gzclose.c:6:
   6/usr/arm-linux-gnueabihf/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
   7   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
   8      |     ^~~~~
   

   Some similar issues in https://bugreports.qt.io suggest to switch from the builtin zlib to a system one. But that doesn’t look like an option for us.

2. hebasto added the label Linux/Unix on Apr 27, 2024
3. hebasto added the label Build system on Apr 27, 2024
4. 
   laanwj commented at 8:02 am on April 28, 2024: member

   This is caused by the 32 to 64 bit time_t transition (for the 2038 epoch problem). It will affect all 32-bit Linux systems.

   I would guess solving this requires a minimal patch to the zlib inside Qt to make the right combination of defines. i’ll take a look at it.

5. laanwj assigned laanwj on Apr 28, 2024
6. laanwj referenced this in commit 17db8e3fc5 on Apr 28, 2024
7. laanwj referenced this in commit e4c1a0c629 on Apr 28, 2024
8. laanwj referenced this in commit b1bd98166d on Apr 28, 2024
9. laanwj referenced this in commit 2fb0092a9c on Apr 28, 2024
10. laanwj referenced this in commit 2e266f33b5 on Apr 29, 2024
11. fanquake closed this on Apr 30, 2024

    ---

12. fanquake referenced this in commit ad42d63519 on Apr 30, 2024
13. fanquake referenced this in commit a995902d60 on Apr 30, 2024

Contributors
hebasto laanwj

Labels
Linux/Unix Build system