From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-core@gentoo.org, gentoo-dev@gentoo.org
Subject: [gentoo-dev] boostrap.sh problem?
Date: 12 Jul 2003 11:54:49 -0400 [thread overview]
Message-ID: <1058025288.3216.13.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 3800 bytes --]
Dear all,
One of our users, "hunt3r" on #gentoo, is having boostrap fail while
building "sed", which for whatever reason is getting built before
gcc/glibc. You can see his (her? dunno) log at
http://lifeline.sytes.net:8001/emerge.log. Should bootstrap be building
sed? If so, should it build it before gcc and glibc? (I normally
wouldn't post this sort of problem here, but I tend to consider any
failures that our users see during bootstrap to be show-stoppers for our
1.4 release.)
Hmmm, is it possible that his build fails because he has "static" in
USE? I haven't looked at the new bootstrap script very carefully to see
how it filters USE flags.
The specific sed error he's getting is:
10:39 <hunt3r> gcc -mcpu=pentium2 -O2 -pipe -static -o sed sed.o
compile.o
execute.o regex.o fmt.o ../lib/libsed.a
10:39 <hunt3r>
./usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/../../../../i586-pc-lin
ux-gnu/bin/ld: cannot find -lc
10:39 <hunt3r> collect2: ld returned 1 exit status
10:39 <hunt3r> make[2]: *** [sed] Error 1
10:39 <hunt3r> make[2]: Leaving directory
`/var/tmp/portage/sed-4.0.7/work/sed-4.0.7/sed'
10:39 <hunt3r> make[1]: *** [all-recursive] Error 1
10:39 <hunt3r> make[1]: Leaving directory
`/var/tmp/portage/sed-4.0.7/work/sed-4.0.7'
10:39 <hunt3r> make: *** [all] Error 2
10:39 <hunt3r> !!! ERROR: sys-apps/sed-4.0.7 failed.
10:39 <hunt3r> !!! Function src_compile, Line 28, Exitcode 2
10:39 <hunt3r> !!! Static build failed
and his emerge --info is:
10:44 <hunt3r> localhost portage # emerge --info
10:44 <hunt3r> !!! No gcc found. You probably need to 'source
/etc/profile' to
update
10:44 <hunt3r> !!! the environment of this terminal and possibly other
terminals also.
10:44 <hunt3r> Portage 2.0.48-r1 (default-x86-1.4, [unavailable],
glibc-2.3.1-r4)
10:44 <hunt3r>
=================================================================
10:44 <hunt3r> System uname: 2.4.21-0.13mdk i686 Celeron (Mendocino)
10:44 <hunt3r> GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
10:44 <hunt3r> CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config"
10:44 <hunt3r> CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
10:44 <hunt3r> PORTDIR="/usr/portage"
10:44 <hunt3r> DISTDIR="/usr/portage/distfiles"
10:44 <hunt3r> PKGDIR="/usr/portage/packages"
10:44 <hunt3r> PORTAGE_TMPDIR="/var/tmp"
10:44 <hunt3r> PORTDIR_OVERLAY=""
10:44 <hunt3r> USE="berkdb gdbm gnome mad mikmod nls pdflib quicktime
3dfx
3dnow aalib acl alsa apache2 arts apm atlas avi bonobo
cdr cjk
crypt cups curl dga doc dvd emacs encode ethereal flash
gb gd
ggi gif gpm gps gtk gtk2 gtkhtml guile icc imap imlib
ipv6 jack
java jikes jpeg junit kde kerberos krb4 ladcca lcms ldap
leim
libg++ libgda libwww maildir matrox mcal memlimit mmx
motif
mozilla mpeg mule ncurses odbc oggvorbis opengl oss pam
perl
plotutils
10:44 <hunt3r> sasl scanner sdl slang snmp socks5 spell sse ssl static
svga
tcltk tcpd tetex tiff truetype usb wmf X Xaw3d xml xml2
xmms xv
zlib x86"
10:44 <hunt3r> COMPILER="gcc3"
10:44 <hunt3r> CHOST="i686-pc-linux-gnu"
10:44 <hunt3r> CFLAGS="-mcpu=pentium2 -O2 -pipe"
10:44 <hunt3r> CXXFLAGS="-mcpu=pentium2 -O2 -pipe"
10:44 <hunt3r> ACCEPT_KEYWORDS="x86"
10:44 <hunt3r> MAKEOPTS="-j2"
10:44 <hunt3r> AUTOCLEAN="yes"
10:45 <hunt3r> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
10:45 <hunt3r> FEATURES="sandbox ccache"
--
Grant Goodyear <g2boojum@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-07-12 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 15:54 Grant Goodyear [this message]
2003-07-12 16:37 ` [gentoo-dev] Re: [gentoo-core] boostrap.sh problem? Grant Goodyear
2003-07-12 19:22 ` Daniel Robbins
2003-07-12 22:53 ` Mike Frysinger
2003-07-13 2:03 ` Stroller
2003-07-16 2:15 ` Mike Frysinger
2003-07-13 5:18 ` Mike Frysinger
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=1058025288.3216.13.camel@localhost \
--to=g2boojum@gentoo.org \
--cc=gentoo-core@gentoo.org \
--cc=gentoo-dev@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