$ builder -r GLIBC_2_3 glibc.spec

[Radosław Kintzi]

Próbowałem zbudować glibc-2.3.1 (z -r GLIB_2_3). Oto wynik:

i586-pld-linux-gcc -nostdlib -nostartfiles -o /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/elf/lddlibc4  -Wl,-dynamic-linker=/lib/ld-linux.so.2    -Wl,-z,combreloc /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/csu/crt1.o /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/csu/crti.o `i586-pld-linux-gcc --print-file-name=crtbegin.o` /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/elf/lddlibc4.o  -Wl,-rpath-link=/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/math:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/elf:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/dlfcn:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/nss:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/nis:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/rt:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/resolv:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/crypt:/home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/linuxthreads /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/libc.so.6 /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/libc_nonshared.a -lgcc `i586-pld-linux-gcc --print-file-name=crtend.o` /home/users/builder/rpm/BUILD/glibc-2.3.1/builddir/csu/crtn.o
make[2]: Leaving directory `/home/users/builder/rpm/BUILD/glibc-2.3.1/elf'
make[1]: Leaving directory `/home/users/builder/rpm/BUILD/glibc-2.3.1'
+ i586-pld-linux-gcc -o postshell -O2 -march=i586 -s /home/users/builder/rpm/SOURCES/postshell.c
In file included from /usr/include/signal.h:358,
                 from /usr/include/sys/wait.h:30,
                 from /home/users/builder/rpm/SOURCES/postshell.c:71:
/usr/include/bits/sigthread.h:36: storage class specified for parameter `type name'
error: Bad exit status from /var/tmp/rpm-tmp.32406 (%build)

Jak widać samo glibc się zbudowało. Problem jest w programie Michała
(malekith). Czy ten błąd może być spowodowany tym, że 
/usr/include/bits/sigthread.h jest z pakietu glibc-2.2.5-19? Jeżeli tak, 
to jak zbudować nowe glibc? (czy postshell nie powinien sobie włączać 
nagłówków z właśnie budowanego glibc?)

Pozdrawiam,
Radek

PS. Środowisko buildera to ra z gcc-3.2-7 (z zależnościami) z nest-test.

-- 
|: Radosław Kintzi                                                      :|
|: e-mail: redek w eth0.prv.pl :|: home page: coming soon :|: GG: 2199600 :|
|: ==================================================================== :|
|: $#%@    malaga, tikitaki i kasztanki                            @%#$ :|