From: jwsacksteder@ramprecision.com
To: gentoo-alpha@gentoo.org
Subject: [gentoo-alpha] glibc blew up...
Date: Mon, 6 Oct 2003 00:05:18 -0400 [thread overview]
Message-ID: <71650A6F73F1D411BE8000805F65E3CB3B365E@SRV-03> (raw)
After 3 hours of chewing on the bootstrap script, glibc produced the
following message. If you have successfully built glibc-2.3.2-r1, please let
me know.
gcc ../linuxthreads/sysdeps/unix/sysv/linux/alpha/vfork.S -c -I../include
-I. -
I/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/posix -I..
-I../libi
o -I/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere
-I../linuxthread
s/sysdeps/alpha/elf -I../sysdeps/alpha/elf
-I../linuxthreads/sysdeps/unix/sysv/l
inux/alpha -I../linuxthreads/sysdeps/unix/sysv/linux
-I../linuxthreads/sysdeps/p
thread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv
-I../linuxthread
s/sysdeps/unix -I../linuxthreads/sysdeps/alpha
-I../sysdeps/unix/sysv/linux/alph
a/alpha -I../sysdeps/unix/sysv/linux/alpha -I../sysdeps/unix/sysv/linux
-I../sys
deps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman
-I../sysdeps/unix/inet
-I../sysdeps/unix/sysv -I../sysdeps/unix/alpha -I../sysdeps/unix
-I../sysdeps/po
six -I../sysdeps/alpha/fpu -I../sysdeps/alpha -I../sysdeps/wordsize-64
-I../sysd
eps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754
-I../sysdeps
/generic/elf -I../sysdeps/generic -nostdinc -isystem
/usr/lib/gcc-lib/alpha-unk
nown-linux-gnu/3.2.3/include -isystem /usr/include -D_LIBC_REENTRANT
-include ..
/include/libc-symbols.h -DASSEMBLER -o
/var/tmp/portage/glibc-2.3.2-r1/w
ork/glibc-2.3.2/buildhere/posix/vfork.o
../linuxthreads/sysdeps/unix/sysv/linux/alpha/vfork.S: Assembler messages:
../linuxthreads/sysdeps/unix/sysv/linux/alpha/vfork.S:63: Warning: .ent
directiv
e without matching .end
../linuxthreads/sysdeps/unix/sysv/linux/alpha/vfork.S:63: Error: can't
resolve `
0' {.text section} - `L0' {.text section}
make[2]: ***
[/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/posix/v
fork.o] Error 1
make[2]: *** Waiting for unfinished jobs....
../linuxthreads/sysdeps/unix/sysv/linux/fork.c: In function `__libc_fork':
../linuxthreads/sysdeps/unix/sysv/linux/fork.c:39: warning: implicit
declaration
of function `__syscall_fork'
make[2]: Leaving directory
`/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/pos
ix'
make[1]: *** [posix/subdir_lib] Error 2
make[1]: Leaving directory
`/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2'
make: *** [all] Error 2
!!! ERROR: sys-libs/glibc-2.3.2-r1 failed.
!!! Function src_compile, Line 310, Exitcode 2
!!! (no error message)
omega portage #
omega portage #
--
gentoo-alpha@gentoo.org mailing list
next reply other threads:[~2003-10-06 4:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 4:05 jwsacksteder [this message]
2003-10-06 6:07 ` [gentoo-alpha] glibc blew up Mathieu MILLET
2003-10-06 7:08 ` Marc Giger
2003-10-08 1:09 ` Aron Griffis
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 11:51 jwsacksteder
2003-10-06 18:17 ` Mathieu MILLET
2003-10-08 1:10 ` Aron Griffis
2003-10-08 1:58 jwsacksteder
2003-10-08 2:43 ` Aron Griffis
2003-10-08 3:23 jwsacksteder
2003-10-08 3:24 ` Aron Griffis
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=71650A6F73F1D411BE8000805F65E3CB3B365E@SRV-03 \
--to=jwsacksteder@ramprecision.com \
--cc=gentoo-alpha@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