| View previous topic :: View next topic |
| Author |
Message |
Kartoffel
n00b
Joined: 23 Apr 2002
Posts: 29
|
 Posted: Fri Jan 03, 2003 3:49 am Post subject: gcc won't compile |
 |
|
I've been trying to emerge gcc-3.2.1 for a couple of months now. I figured there was a problem with the ebuild and I gave it time to get worked out. Today I tried again and it still doesn't work. I've tried all different cflags and none work. I just tried with the safest set and it still didn't work. It's always the same error and I have no idea what's wrong. It used to work.
I tried searching but came up dry. If there is a post somewhere please post a link. Searching is quite a pain because whenever I search for mulitple words and select "match all words" and hit go Galeon crashes.
My system
Athlon XP 2100
512 ram
plenty of space everywhere
I've tried these cflags and my more extreme ones as well.
CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CFLAGS="-march=pentium3 -O3 -pipe"
| Code: |
/libjava/../gcc -I/var/tmp/portage/gcc-3.2.1/work/gcc-3.2.1/libjava/../libffi/include -I../libffi/include -fno-rtti -fnon-call-exceptions -fdollars-in-identifiers -D__NO_MATH_INLINES -ffloat-store -I/usr/X11R6/include -W -Wall -D_GNU_SOURCE -DPREFIX=\"/usr\" -march=pentium3 -pipe -D_GNU_SOURCE -MD -MT java/net/natInetAddress.lo -MF java/net/natInetAddress.pp -c /var/tmp/portage/gcc-3.2.1/work/gcc-3.2.1/libjava/java/net/natInetAddress.cc -o java/net/natInetAddress.o >/dev/null 2>&1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/var/tmp/portage/gcc-3.2.1/work/build/i686-pc-linux-gnu/libjava'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-3.2.1/work/build/i686-pc-linux-gnu/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.2.1/work/build'
make: *** [bootstrap-lean] Error 2
!!! ERROR: sys-devel/gcc-3.2.1 failed.
|
Thanks,
JP |
|
| Back to top |
|
 |
bonsaikitten
Apprentice
Joined: 01 Jan 2003
Posts: 213
Location: Shanghai, China
|
| Posted: Fri Jan 03, 2003 12:26 pm Post subject: |
|
|
Have you tried non-optimised builds, e.g. -O2 ?
Some packages react badly to aggressive optimization, so try emerging gcc with defensive flags. |
|
| Back to top |
|
|
jukka
Apprentice
Joined: 06 Jun 2002
Posts: 249
Location: Zurich, Switzerland
|
| Posted: Fri Jan 03, 2003 1:34 pm Post subject: |
|
|
| bonsaikitten wrote: | | Have you tried non-optimised builds, e.g. -O2 ? |
'-O2' is pronounced 'optimise, level two'. why should this be non-optimised?
| Quote: | | Some packages react badly to aggressive optimization, so try emerging gcc with defensive flags. |
correct, but gcc ebuilds strip flags anyway, so this won't work... sorry potato, can't help either! |
|
| Back to top |
|
|
Kartoffel
n00b
Joined: 23 Apr 2002
Posts: 29
|
| Posted: Fri Jan 03, 2003 3:41 pm Post subject: |
|
|
well just for grins I tried with the -o2 and even with cflags="" the compile always stops at the same place. I also tried rm -r /var/tmp/portage/gcc*
still looking for answers
Jeff |
|
| Back to top |
|
|
|
Portage & Programming
