Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 7110 - glibc exits build with error
Summary: glibc exits build with error
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Martin Schlemmer (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-27 06:21 UTC by Christoph Mertins
Modified: 2003-02-04 19:42 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Mertins 2002-08-27 06:21:55 UTC
/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/elf/ld-linux.so.2
--library-path /var/tmp/portage/glibc-2
.2.5-r6/work/glibc-2.2.5/buildhere:/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/math:/var/tmp/portage/
glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/elf:/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/dlfcn:/var/
tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/nss:/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere
/nis:/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/rt:/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/
buildhere/resolv:/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/crypt:/var/tmp/portage/glibc-2.2.5-r6/wo
rk/glibc-2.2.5/buildhere/linuxthreads
/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/sunrpc/rpcgen -Y ..
/scripts -c rpcsvc/bootparam_prot.x -o
/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/sunrpc/xbootparam_
prot.T
make[2]: ***
[/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/buildhere/sunrpc/xbootparam_prot.stmp]
Illegal instru
ction
make[2]: Leaving directory `/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5/sunrpc'
make[1]: *** [sunrpc/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.2.5-r6/work/glibc-2.2.5'
make: *** [all] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 81, Exitcode 2
!!! (no error message)

!!! emerge aborting on  /usr/portage/sys-libs/glibc/glibc-2.2.5-r6.ebuild
Comment 1 Martin Schlemmer (RETIRED) gentoo-dev 2002-08-27 20:12:25 UTC
What version:  portage
               binutils
               gcc

How much free space on all partitions, and what is PORTAGE_TMPDIR set to
(in /etc/make.conf or /etc/make.globals)?

What cpu do you have, and what is your CFLAGS and CXXFLAGS set to?

Anything else that can be relevant?

Please, you need to be a bit more specific if you want help, thanks.
Comment 2 Martin Schlemmer (RETIRED) gentoo-dev 2002-09-08 03:35:38 UTC
This was portage issues.
Comment 3 Seemant Kulleen (RETIRED) gentoo-dev 2002-10-10 15:57:35 UTC
<danarmak> oh great, bootstrap failed on glibc with illegal instruction :-(
<danarmak> it says something like, make [2] ***
[$S/buildhere/sunrpc/xbootparam_prot.T] Illegal instruction

<danarmak> seems this is bug #7110
<GenBot> danarmak: Bug http://bugs.gentoo.org/show_bug.cgi?id=7110 cri, P2, PC,
azarah@gentoo.org, RESO, FIXE, glibc exits build with error
<danarmak> which was closed by azarah with the comment "this was portage
issues". i have portage 2.0.38 here. does anyone know what this bug/fix was about?
Comment 4 Seemant Kulleen (RETIRED) gentoo-dev 2002-10-10 15:58:07 UTC
<danarmak> seemant: thanks, please say there that the surest way of reaching me
atm is leaving an irc memo; il'l check the bug comments too
Comment 5 Martin Schlemmer (RETIRED) gentoo-dev 2002-10-12 14:09:52 UTC
Was mad or something.  Cannot remember what this boiled down to.

The most common thing for error like this is that something was compiled
with instructions that your CPU do not support (mmx on non mmx system, or
sse or whatever).
Comment 6 Dan Armak (RETIRED) gentoo-dev 2002-10-17 15:16:14 UTC
Well, I didn't have the resources to investigate at the time (n working system  
and I needed one very quickly) so I gave up the gcc2 compiling speed and built   
a system with gcc3. Not a hitch. This problem was reproducible with gcc2 and   
profile default-1.0 though, and I can see no reason why there would be illegal 
isntructions in there (it was a k6-2 compiled with the right default optims). 
 
Anyway, I've enough on my hands and won't be trying to reproduce this anytime 
soon, so I guess it can be closed again since noone else has reported it.