From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] glibc-2.3.6 fails to compile (in a vserver)
Date: Thu, 20 Sep 2007 12:35:21 +0200 [thread overview]
Message-ID: <200709201235.21468.alan@linuxholdings.co.za> (raw)
Hi,
A glibc upgrade from 2.3.5-r2 to 2.3.6-r5 inside a vserver is failing on
me.
It's a new install using a 20060317 stage3 built for vservers by hollow.
I need a 2.3 glibc for the app that will run in it, hence the very old
stage3. Running a later glibc is not an option.
The stage originally had baselayout-vserver1.1.?, I've changed this to
baselayout-1.13.0_alpha2 because
http://www.gentoo.org/proj/en/vps/vserver-howto.xml implies it should
work.
USE settings for glibc:
nazgul-master / # emerge -av glibc
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-libs/glibc-2.3.6-r5 [2.3.5-r2]
USE="-build -erandom -glibc-compat20 -glibc-omitfp (-hardened)
(-multilib) -nls* (-nptl) (-nptlonly) -profile (-selinux)
(-linuxthreads-tls%) (-pic%) (-userlocales%)" 0 kB
The compile errors:
i686-pc-linux-gnu-gcc ../sysdeps/generic/sigjmp.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -fno-strict-aliasing -march=pentium-m -pipe -mpreferred-stack-boundary=2 -I../include -I. -I/var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads/setjmp -I.. -I../libio -I/var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../libidn/sysdeps/unix -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include -isystem /usr/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -o /var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads/setjmp/sigjmp.o -MD -MP -MF /var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads/setjmp/sigjmp.o.dt -MT /var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads/setjmp/sigjmp.o
../sysdeps/i386/elf/setjmp.S: Assembler messages:
../sysdeps/i386/elf/setjmp.S:63: Error: junk at end of line, first
unrecognized character is `1'
../sysdeps/i386/elf/setjmp.S:64: Error: junk at end of line, first
unrecognized character is `1'
../sysdeps/i386/elf/setjmp.S:65: Error: junk at end of line, first
unrecognized character is `1'
../sysdeps/i386/elf/setjmp.S:66: Error: unrecognized symbol type ""
../sysdeps/i386/elf/setjmp.S:66: Error: junk at end of line, first
unrecognized character is `1'
../sysdeps/i386/elf/setjmp.S:67: Error: junk at end of line, first
unrecognized character is `1'
../sysdeps/i386/elf/setjmp.S:70: Error: expected comma after name `'
in .size directive
make[2]: ***
[/var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads/setjmp/setjmp.o]
Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/glibc-2.3.6/setjmp'
make[1]: *** [setjmp/subdir_lib] Error 2
make[1]: Leaving directory
`/var/tmp/portage/sys-libs/glibc-2.3.6-r5/work/glibc-2.3.6'
make: *** [all] Error 2
alan
--
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?
Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-09-20 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 10:35 Alan McKinnon [this message]
2007-09-20 11:49 ` [gentoo-user] glibc-2.3.6 fails to compile (in a vserver) Alan McKinnon
2007-09-20 12:42 ` Bo Ørsted Andresen
2007-09-21 12:42 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709201235.21468.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox