View previous topic :: View next topic |
Author |
Message |
dood Guest
|
Posted: Tue Jun 04, 2002 8:09 pm Post subject: error on stage 1 compile, bootstrap.sh help! |
|
|
heres the error msg i get.
make [2]: ***
[/var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5/buildhere/sunrpc/xbootparam_prot.stmp] Illegal instruction
make [2]: *** Waitng for unfinished jobs...
make [2]: Leaving directory '/var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5/sunrpc'
make [1]: *** [sunrpc/others] Error 2
make [1]: Leaving directory 'var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5'
make: *** [all] Error 2
!!! ERROR: The ebuild did not complete sucessfully.
!!! Function src_compile, Line 14, Exitcode 2
!!! (no error message)
!!! emerge aborting on /user/portage/sys-libs/glibc/glibc-2.2.5-r2.ebuild
#
oh and i have a gcc version 2.95.3 20010315 (release) |
|
Back to top |
|
|
delta407 Bodhisattva
Joined: 23 Apr 2002 Posts: 2876 Location: Chicago, IL
|
Posted: Sat Jun 08, 2002 3:09 am Post subject: |
|
|
"Illegal instruction" means you tried to execute machine code that your CPU didn't understand. Your hard drive could be going bad, not cleanly unmounted, or (most likely) you tried to compile for an architecture that does not match your system. (Code designed for a Pentium 3 will not run on a 486.) Make sure your /etc/make.conf is set up right. |
|
Back to top |
|
|
Scrapz n00b
Joined: 06 Jun 2002 Posts: 21
|
Posted: Sun Jun 09, 2002 1:39 am Post subject: |
|
|
...or make sure you're not using some funky optimizations in /etc/make.conf - just use one of the basic examples in there for now... if they're too rugged they will not compile, or worse, compile broken binaries.
TTFN,
Scrapz |
|
Back to top |
|
|
delta407 Bodhisattva
Joined: 23 Apr 2002 Posts: 2876 Location: Chicago, IL
|
Posted: Sun Jun 09, 2002 3:41 am Post subject: |
|
|
Funky optimizations wouldn't cause unrecognized machine code, which is what "illegal instruction" means. It would just optimize the code into oblivion, where order is exchanged for chaos and segfaults reign supreme. More likely is that there's the wrong architecture supplied in /etc/make.conf, or that a stage3 tarball was used on a pre-686 system. |
|
Back to top |
|
|
|