Hi,
I'm trying to build the glibc package from Ubuntu in the
buildservice.
The build failed in the testsuite at:
---
[ 6235s] x86_64-linux-gnu-gcc -m32 -shared -o /usr/src/packages/BUILD/build-tree/amd64-i386/elf/tst-big-note-lib.so -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both /usr/src/packages/BUILD/build-tree/amd64-i386/elf/tst-big-note-lib.o
[ 6235s] /usr/bin/ld: cannot find crti.o: No such file or directory
---
I was told for -m32 the crti.o is delivered by the 32bit development
package. Which means you need glibc to build glibc. crti.o is provided
by "libc6-dev-x32" on Ubuntu.
I tried to add:
%ifarch %ix86
Preinstall: libc6-dev-x32
Support: libc6-dev-x32
%endif
But this seems to have no effect and I did not understand why.
The buildinfo says:
...
<subpack>libc6-dev-x32</subpack>
...
On Monday 2022-05-02 17:24, Marcus Schäfer wrote:
--- [ 6235s] x86_64-linux-gnu-gcc -m32 -shared -o /usr/src/packages/BUILD/build-tree/amd64-i386/elf/tst-big-note-lib.so -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both /usr/src/packages/BUILD/build-tree/amd64-i386/elf/tst-big-note-lib.o [ 6235s] /usr/bin/ld: cannot find crti.o: No such file or directory ---
I was told for -m32 the crti.o is delivered by the 32bit development package. Which means you need glibc to build glibc. crti.o is provided by "libc6-dev-x32" on Ubuntu.
Is it for real? Just from the name alone, I would expect that "...somethingsomething-x32" be meant to be used in conjunction with the -mx32 flag, not -m32.
On Mai 02 2022, Marcus Schäfer wrote:
I was told for -m32 the crti.o is delivered by the 32bit development package.
That doesn't make sense, crti.o is built as part of glibc itself. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Hi,
That doesn't make sense, crti.o is built as part of glibc itself.
Thanks for the information so far. The compilation succeeds and the testsuite runs through. At the end of the tests there is a summary and it contains two failed tests which I assume are the reason for the overall failed state, not sure though Since this is the original source tarball for glibc as it is build in some buildsystem for Debian, I assume the failed tests are still related to the environment. I have attached the testsuite summary and maybe Jan or Andreas can you give me another hint what might be the reason for the failed tests ? Thanks much Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer Brunnenweg 18 Tel: +49 7562 905437 D-88260 Argenbühl Germany -------------------------------------------------------
participants (3)
-
Andreas Schwab
-
Jan Engelhardt
-
Marcus Schäfer