Hmm, there is a very suspicious dir showing up:
echo "#include " | gcc -E -Wp,-v -
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/include"
#include "..." search starts here:
#include
Chances are high that this -fixed was brought in via a bug/discussion,
lets check the changelog to find it.
9 gcc-9 (9.3.0-1) unstable; urgency=medium
...
16 * Stop shipping the include-fixed directory.
...
2
Same on x86 is working!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867316
Title:
FTFBS in Focal armhf/ppc64/s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
this still had one indirection
this is even better:
$ cat > test.c << EOF
> /*
> * Test FTBFS 1867316
> */
>
> #include
> EOF
ubuntu@focal-ftbfs:~/chrony-3.5$ gcc -c test.c
In file included from test.c:5:
/usr/include/limits.h:124:26: error: no include path in which to search for
limits.h
1
Really ... does that mean anything including sys/param.h is FTBFS now?
$ cat > test.c << EOF
/*
* Test FTBFS 1867316
*/
#include
EOF
$ s390x-linux-gnu-gcc -g -O2 -Wformat -Werror=format-security -pthread
-Wdate-time -D_FORTIFY_SOURCE=2 -c test.c
In file included from /usr/include/s390x-lin
I first saw this with a chrony build, but it seems not a chrony problem I guess.
To check I installed in focal-proposed:
$ apt build-dep chrony
On amd64 and s390x.
We have:
=> /usr/include/resolv.h:56:#include
=> /usr/include/s390x-linux-gnu/sys/param.h:26:#include
=> /usr/include/limits.h:1
