Gentoo Archives: gentoo-amd64

From: Beso <givemesugarr@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Can not compile gcc
Date: Fri, 14 Nov 2008 19:24:28
Message-Id: d257c3560811141124l457f52dei152b3229c6ae31f2@mail.gmail.com
In Reply to: Re: [gentoo-amd64] Can not compile gcc by Mansour Al Akeel
1 2008/11/14 Mansour Al Akeel <mansour.alakeel@×××××.com>:
2 > I have already initiated the build again after I modified the USE flags to
3 > the defaults that came with the installation cd. Here's the dfaults:
4 > ==================================================================
5 > # These settings were set by the catalyst build script that automatically
6 > # built this stage.
7 > # Please consult /etc/make.conf.example for a more detailed example.
8 > CFLAGS="-O2 -pipe"
9 > CXXFLAGS="-O2 -pipe"
10 > # WARNING: Changing your CHOST is not something that should be done lightly.
11 > # Please consult http://www.gentoo.org/doc/en/change-chost.xml before
12 > changing.
13 > CHOST="x86_64-pc-linux-gnu"
14 > # These are the USE flags that were used in addition to what is provided by
15 > the
16 > # profile used for building.
17 > USE="mmx sse sse2"
18 > =================================================================
19 >
20 > I am still waiting to see the results. When the error occured I was using
21 > the following make.conf:
22 >
23 > ======================================================
24 > CFLAGS="-march=athlon64 -O2 -pipe"
25 > CXXFLAGS="${CFLAGS}"
26 >
27 > CHOST="x86_64-pc-linux-gnu"
28 >
29 > MAKEOPT="-j2"
30 > FEATURES="ccache"
31 >
32 > USE="X aac aiglx alsa aoss asf bzip2 cairo dbus dvd emerald fam firefox gif
33 > glitz gnome gstreamer gtk hal java jpeg mad mp3 mp4 new-login nptl
34 > nptlonly nsplugin opengl pdf png samba spell sqlite svg symlink threads
35 > tiff truetype unicode x264 xcomposite xinerama xml xorg xscreensaver xv
36 > xvid -arts -eds -esd -fortran -ipv6 -kde -qt3 -qt4"
37 >
38 > VIDEO_CARDS="NVIDIA"
39 > ===================================================
40 >
41 > I should have kept a back up of the build.log but if anyone needs it, I can
42 > do emerge again, and send you the file, as I have this strong feeling that
43 > the build I am doing now will fail as well.
44 > Thank you all.
45 >
46 >
47 > On Fri, Nov 14, 2008 at 2:40 PM, Justin <justin@×××××××××.net> wrote:
48 >>
49 >> Branko Badrljica schrieb:
50 >> > Justin wrote:
51 >> >> Barry Schwartz schrieb:
52 >> >>
53 >> >>> Mansour Al Akeel <mansour.alakeel@×××××.com> skribis:
54 >> >>>
55 >> >>>> Any idea ?
56 >> >>>>
57 >> >>> If you use ccache, try emptying it.
58 >> >>>
59 >> >>>
60 >> >>>
61 >> >>>
62 >> >> I think there is something else wrong, because it fails in the
63 >> >> configure
64 >> >> phase.
65 >> >>
66 >> >> Send us an emerge --info output, please.
67 >> >>
68 >> >>
69 >> >
70 >> > I'm not an expert, but it seems that it was trying to compile 64-bit
71 >> > test code with -m32 flag:
72 >> >
73 >> > >The log file:
74 >> > >checking for x86_64-pc-linux-gnu-gcc...
75 >> > /var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc
76 >> > -B/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/
77 >> > -B/usr/x86_64-pc-linux-gnu/bin/ >-B/usr/x86_64-pc-linux-gnu/lib/
78 >> > -isystem /usr/x86_64-pc-linux-gnu/include -isystem
79 >> > /usr/x86_64-pc-linux-gnu/sys-include -m32
80 >> >
81 >> >
82 >> > Perhaps he should check his make.conf for CHOST and CLAGS ?
83 >> >
84 >> Sharp eyed guy!!
85 >>
86 >
87 >
88
89
90 hmm. you seem to have a problem with gcc. try removing the ccache
91 feature and compile it without. usually this works.
92
93 --
94 dott. ing. beso