Re: [gentoo-amd64] Can not compile gcc

[Mansour Al Akeel]

I have already initiated the build again after I modified the USE flags to
the defaults that came with the installation cd. Here's the dfaults:
==================================================================
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-O2 -pipe"
CXXFLAGS="-O2 -pipe"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before
changing.
CHOST="x86_64-pc-linux-gnu"
# These are the USE flags that were used in addition to what is provided by
the
# profile used for building.
USE="mmx sse sse2"
=================================================================

I am still waiting to see the results. When the error occured I was using
the following make.conf:

======================================================
CFLAGS="-march=athlon64 -O2 -pipe"
CXXFLAGS="${CFLAGS}"

CHOST="x86_64-pc-linux-gnu"

MAKEOPT="-j2"
FEATURES="ccache"

USE="X aac aiglx alsa aoss asf bzip2 cairo dbus dvd emerald fam firefox gif
     glitz gnome gstreamer gtk hal java jpeg mad mp3 mp4 new-login nptl
     nptlonly nsplugin opengl pdf png samba spell sqlite svg symlink threads
     tiff truetype unicode x264 xcomposite xinerama xml xorg xscreensaver xv
     xvid -arts -eds -esd -fortran -ipv6 -kde -qt3 -qt4"

VIDEO_CARDS="NVIDIA"
===================================================

I should have kept a back up of the build.log but if anyone needs it, I can
do emerge again, and send you the file, as I have this strong feeling that
the build I am doing now will fail as well.
Thank you all.


On Fri, Nov 14, 2008 at 2:40 PM, Justin <justin@×××××××××.net> wrote:

> Branko Badrljica schrieb:
> > Justin wrote:
> >> Barry Schwartz schrieb:
> >>
> >>> Mansour Al Akeel <mansour.alakeel@×××××.com> skribis:
> >>>
> >>>> Any idea ?
> >>>>
> >>> If you use ccache, try emptying it.
> >>>
> >>>
> >>>
> >>>
> >> I think there is something else wrong, because it fails in the configure
> >> phase.
> >>
> >> Send us an emerge --info output, please.
> >>
> >>
> >
> > I'm not an expert, but it seems that it was trying to compile 64-bit
> > test code with -m32 flag:
> >
> > >The log file:
> > >checking for x86_64-pc-linux-gnu-gcc...
> > /var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc
> > -B/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/
> > -B/usr/x86_64-pc-linux-gnu/bin/ >-B/usr/x86_64-pc-linux-gnu/lib/
> > -isystem /usr/x86_64-pc-linux-gnu/include -isystem
> > /usr/x86_64-pc-linux-gnu/sys-include  -m32
> >
> >
> > Perhaps he should check his make.conf for CHOST and CLAGS ?
> >
> Sharp eyed guy!!
>
>