this still had one indirection
this is even better:
$ cat > test.c << EOF
> /*
> * Test FTBFS 1867316
> */
>
> #include <limits.h>
> 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
124 | # include_next <limits.h>
| ^
I'll move that to the bug description and flag the packages owning the
involved files
** Description changed:
+ This seems an almost global FTBFS with anything that includes limits.h
+
+ $ cat > test.c << EOF
+ > /*
+ > * Test FTBFS 1867316
+ > */
+ >
+ > #include <limits.h>
+ > 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
+ 124 | # include_next <limits.h>
+ | ^
+
+ Interestingly this fails on armhf/ppc64/s390x but works on x86.
+
+
+ --- started as a chrony FTBFS despite tetsing a few hours before ---
+
For bug 1866753 we built this yesterday in a proposed PPA and things worked!
Now today on the final upload it failed to build on armhf/ppc64/s390x.
In file included from /usr/include/powerpc64le-linux-gnu/sys/param.h:26,
- from /usr/include/resolv.h:56,
- from nameserv.c:34:
+ from /usr/include/resolv.h:56,
+ from nameserv.c:34:
/usr/include/limits.h:124:26: error: no include path in which to search for
limits.h
- 124 | # include_next <limits.h>
- | ^
+ 124 | # include_next <limits.h>
+ | ^
make[1]: *** [Makefile:108: nameserv.o] Error 1
The same error on all of them.
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bot-stop-nagging
** Also affects: gcc-9 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: chrony (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867316
Title:
FTFBS in Focal armhf/ppc64/s390x
Status in chrony package in Ubuntu:
Invalid
Status in gcc-9 package in Ubuntu:
New
Status in glibc package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
This seems an almost global FTBFS with anything that includes limits.h
$ cat > test.c << EOF
> /*
> * Test FTBFS 1867316
> */
>
> #include <limits.h>
> 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
124 | # include_next <limits.h>
| ^
Interestingly this fails on armhf/ppc64/s390x but works on x86.
--- started as a chrony FTBFS despite tetsing a few hours before ---
For bug 1866753 we built this yesterday in a proposed PPA and things worked!
Now today on the final upload it failed to build on armhf/ppc64/s390x.
In file included from /usr/include/powerpc64le-linux-gnu/sys/param.h:26,
from /usr/include/resolv.h:56,
from nameserv.c:34:
/usr/include/limits.h:124:26: error: no include path in which to search for
limits.h
124 | # include_next <limits.h>
| ^
make[1]: *** [Makefile:108: nameserv.o] Error 1
The same error on all of them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1867316/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
