You are not logged in.
Pages: 1
Hey guys, after the latest update, gcc seems to be broken. Heres the error I get when trying to build something:
[wsduvall@asar growth]$ make
gcc -O3 -Wall -lm -o growth main.c lattice.c random.c
gcc: Internal error: Bus error (program as)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [growth] Error 1
Heres the kernel I'm using:
[wsduvall@asar growth]$ uname -a
Linux asar 2.6.31-ARCH #1 SMP PREEMPT Tue Nov 10 19:01:40 CET 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz GenuineIntel GNU/Linux
The log from the update is can be found here: http://pastebin.com/f2c4ac314
If you would like more information let me know. Thanks!
Last edited by ackthet (2009-11-13 16:45:23)
Offline
Is the code something that is available so we can try to replicate? Try changing -O3 to -O2
Offline
Hi
Please check the md5 sum of these files:
77fff4c44c2e2368e9d23fd128ffc9eb /usr/bin/as
8ae152554c7335ff7e3cc375b744a2b2 /usr/lib/libopcodes-2.20.0.20091101.so
ab04b7fc1bae84e594ddf9063ecc7028 /usr/lib/libbfd-2.20.0.20091101.so
Offline
djgera: /usr/bin/as returns a different checksum... but the other two seem ok. I reinstalled binutils and the issue is fixed! Thanks all! Any idea what caused the issue?
Allan: The code is availible, however, that code builds on other machines, and I'm having trouble building anything at all.
Last edited by ackthet (2009-11-13 16:14:15)
Offline
djgera: /usr/bin/as returns a different checksum... but the other two seem ok. I reinstalled binutils and the issue is fixed! Thanks all! Any idea what caused the issue?
A corrupted file? A quick Google search says this is a binutils issue.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
You are welcome.
What cause this: I don't know why. I didn't experience this. I see sometimes the exact issue on this forum [#1]. The weird is that if a package is downloaded ok and md5sum is checked by pacman, why some files are corrupted. you have a hard reset recently your machine? This is one possible cause that can explain this.
Offline
Pages: 1