[Bug 1843743] Re: klibc ftbfs in eoan
Ben Hutchings
ben at decadent.org.uk
Mon Oct 14 18:04:36 UTC 2019
Steve Langasek wrote:
> The root failure is:
> objcopy -O binary usr/klibc/syscalls/typesize.o usr/klibc/syscalls/typesize.bin
> mkdir -p usr/include/klibc/; perl /tmp/klibc-2.0.6/usr/klibc/syscalls.pl -2 usr/klibc/syscalls/SYSCALLS.i /tmp/klibc-2.0.6/usr/klibc/arch/x86_64/sysstub.ph x86_64 64 usr/klibc/syscalls/syscalls.nrs usr/klibc/syscalls usr/include/klibc/havesyscall.h usr/klibc/syscalls/typesize.bin > usr/klibc/syscalls/syscalls.mk || ( rm -f usr/klibc/syscalls/syscalls.mk ; exit 1 )
> [...]
> /tmp/klibc-2.0.6/usr/klibc/syscalls.pl: usr/klibc/syscalls/typesize.bin: magic number not found
Thanks, I wasn't able to access the build log so I didn't see this.
Adam Conrad wrote:
> 2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at 5.2), with the latter being more likely.
I tested upstream with Linux 5.3 headers, and klibc doesn't use glibc,
so it's unlikely to be either of those.
The best guess I can come up with is that there's something different
about the compiler defaults you're using that causes "objcopy -O binary"
to not include static data in the output. objcopy itself probably isn't
the difference as Debian unstable and Ubuntu eoan seem to have the same
version of binutils.
(But I wonder whether the objcopy is even necessary. syscalls.pl doesn't
require the magic number to be at the beginning of the file, so
presumably it would also work with a regular ELF object file.)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1843743
Title:
klibc ftbfs in eoan
Status in klibc package in Ubuntu:
Confirmed
Status in klibc source package in Eoan:
Confirmed
Bug description:
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-
amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz
gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<<PKGBUILDDIR>>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<<PKGBUILDDIR>>/usr/include/bits64 -Iusr/include/bits64 -I/<<PKGBUILDDIR>>/usr/klibc/../include -Iusr/klibc/../include -I/<<PKGBUILDDIR>>/usr/include -Iusr/include -I/<<PKGBUILDDIR>>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory
8 | #include <klibc/havesyscall.h>
| ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/<<PKGBUILDDIR>>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1
make[3]: *** [/<<PKGBUILDDIR>>/./Kbuild:9: all] Error 2
make[2]: *** [Makefile:118: klibc] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions
More information about the foundations-bugs
mailing list