Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 46356 - Illegal instruction on tbz2tool.c while emerging portage-2.0.50-r1
Summary: Illegal instruction on tbz2tool.c while emerging portage-2.0.50-r1
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 All
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-31 06:16 UTC by Frank Scholten
Modified: 2004-04-01 05:35 UTC (History)
0 users

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 Frank Scholten 2004-03-31 06:16:35 UTC
Context:

- Booted with LiveCD 1.4_rc4
- Downloaded stage-2-x86-20040218 tarball
- Followed all steps of gentoo install up to and including `emerge sync`

Reproducible behaviour:

1. $ emerge portage
2. I get the following error: 

>>> Source unpacked.
tbz2tool.c: In function `exists':
tbz2tool.c:25: internal compiler error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
Preprocessed source stored into  /var/tmp/portage/portage-2.0.50-r1/temp/ccmuNXMn.out file, please attach this to your bugreport
./create-localdecls
...

I'm in the install phase and don't have any tools with which I can move the preprocessed source file to this machine for copy pasting it into this bug report. Sorry about that. I tried emering ncftp & ftp to try to ftp is but emerging these programs also failed.
Comment 1 Sven Vermeulen (RETIRED) gentoo-dev 2004-04-01 03:56:44 UTC
Illegal instructions in this case can be the result of defunct hardware. Please check your memory (memtest) and make sure you don't overclock your CPU. Check if the cooling mechanism for your system functions correctly. 

What optimization flags did you use? Using overagressive flags can cause this behaviour as well. 
Comment 2 Frank Scholten 2004-04-01 05:16:53 UTC
You're right about defunct hardware. Thanks! I did a memtest and got 638 errors in the upper region of my memory. 

I guess this bugreport is obsolete.
Comment 3 Sven Vermeulen (RETIRED) gentoo-dev 2004-04-01 05:35:46 UTC
Okay, invalidating then.