My system is brand new. I read about fixing my CFLAGS. Easier said than done.
I never had a 64bit system, so i don't exactly know how.

/etc/make.conf

Code:

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-march=corei7-avx -O2 -pipe"
CXXFLAGS="${CFLAGS}"
# 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"
MAKEOPTS="-j9"

# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="mmx sse sse2"
ACCEPT_LICENSE="Broadcom"

Comment out the CFLAGS variable in make.conf and see if the problem goes away. If so, it probably means that the compiler you're using doesn't support the exact -march you're trying to use. Try that & report back, please.

- John_________________I can confirm that I have received between 0 and 499 National Security Letters.

Similar issue - not sure how to fix it. Can anyone suggest anything, please?

I ran emerge -auD world on a previously working system which had not been updated for about 3 weeks.
This upgraded gcc-config-1.4.1-r1 to gcc-config-1.5-r2
sys-devel/gcc-4.5.3-r1 to sys-devel/gcc-4.5.3-r2
sys-devel/gcc-4.4.5 to sys-devel/gcc-4.4.6-r1
glibc was not updated
The emerge was completely successful, in that it completed without error.
I did not run revdep-rebuild at the time but I did use dispatch-conf and I have subsequently rebooted
Now the C compiler is not working. I have a few other miscellaneous breakages as well (firefox).

The cause was vmware PCoIP client 32-bit software I was obliged to install. It recreated a /usr/lib containing just its own files. I removed this directory and symlinked /usr/lib64 to /usr/lib, which is the way I presume things are mean't to be. Then running env-update seems to have got everything working again.

Background:
* Installed AVR cross-tools for Arduino (the Atmel package). After a while tried to follow "Gentoo on Beagle" which failed
(another matter altogether?).
* Tried this operation with several versions of GCC. Various modes of failure, but at the same place.
* Ran the configure generated by the ebuild directly; configures fine.

Questions:

* Freely admitting my setup is complex and messy and the trouble I am in is of my own doing, can someone help me
out of this mess?
* Where does the -V come into CFLAGS? It is not in /etc/make.conf, not in the .ebuild script, not in the environment.
This -V is not set up correctly for gcc 2.5, and is gone from gcc 2.6.
* Who/what specifies that GLIBC_2.4 is needed, and why?
Why not newer version (2.12 is installed here).
* I can see the string "GLIBC_2.4" in /lib64/libc.xxx. So why is the test a.out complaining?
* How can I "force" recognition of this label?

It is the same for me. I can not compile anything.
This is going to take a long time to explain, so please bare with me.
Many months ago, I installed a flash plugin for Epiphany, it installed a /lib32 and /usr/lib32 folder on my system.
This did not cause any problems until I ran a full system rebuild, and when portage got to baselayout, it complained about the /lib32 library.
So I merged the folder into lib and likewise with /usr/lib32, before deleting the /lib32 and /usr/lib32 folders.
Baselayout compiled fine after that. The only thing is, (which I don't think is too much of a problem), whenever I compile anything portage
gives me the message at the end of every build saying....

Code:

/sbin/ldconfig/libpcre.so.0 is not a symlink
/sbin/ldconfig/libudev.so.0 is not a symlink

So, I thought I would remove the offending file, in this case libcre.so.0 from my lib folder, (ouch I can hear some people say)
the file did have a little "link" arrow and it was pointing to libprce.so.1.0.1 (i think), but portage was telling me it wasn't a symlink.
It won't come as a surprise to those in the know, that removing the libpcre file has killed my compiler.
As soon as I realise this, I immediately put it back. By this time I had to manually pull it over from my NFS portage server and my portage database was sane again.
I have switched between gcc-4.4.7 4.5.4 and 4.6.3, ran env-update && source /etc/profile on each occasion, and yet
portage can't build anything.
Below is the config.log for when I try to build binutils.

Code:

It was created by configure, which was
generated by GNU Autoconf 2.64. Invocation command line was

I spent over 4 hours last night trying to chroot into Gentoo using a Live DVD, as I read on these forums that it might be possible to rebuild GCC and fix things from such an environment.
But my motherboard does not like playing any Live DVD's and just ALL my live disks complain about not being able to see the CD-ROM.
So I waste a lot of time trying to create a bootable USB flash drive (using windows) and all the apps I tried just crashed. I have tried all sorts of settings in the bios, (I don't seem to have and IDE setting in the BIOS).
So hey ho, I just can't get into Gentoo via Live DVD.
Today, portage is no longer seeing my NFS server, so whenever I call on emerge, I see the following:

Been running Gentoo since February 2009, and never had to re-install. I have been through a few system borks, but, at least, been able to compile.
I really don't know what to do now, as I have looked at other posts on here, and I can't make head nor tail of it.
How the hell do I compile, when my system can't build GCC? _________________Whatever you do, do it properly!

As it was explain by someone with better teaching skill then me, i will tell you to search with keyword "tinderbox" and author NeddySeagoon in the forum, you will get more than one good answer for sure. I suppose the alternate answer would be "With binary" so.
(hey! you never said without internet connection right)

Hey Krinn, yes I have an internet connection. Right now I am trying to get my head round "emerging" a package. I pulled in the package from tinderbox, but I can't emerge anything as my NFS Portage is trying do downgrade the database everytime I call "emerge"._________________Whatever you do, do it properly!

Any of those should be considered dangerous, but if i were you, i would try the --package-moves=n one
posting it here so you see why i would (still don't forget, i have warm you all of those might hurt your cat badly, but you have no cat no ?)

Quote:

--package-moves [ y | n ]
Perform package moves when necessary. This option is enabled by default. Package moves are typi‐
cally applied immediately after a --sync action. They are applied in an incremental fashion, using
only the subset of the history of package moves which have been added or modified since the previ‐
ous application of package moves.

WARNING: This option should remain enabled under normal circumstances. Do not disable it unless
you know what you are doing.

NOTE: The fixpackages(1) command can be used to exhaustively apply the entire history of package
moves, regardless of whether or not any of the package moves have been previously applied.

whenever I call emerge.
The only other time I have seen output like is when portage could not see the portage NFS share on my server. I repeat, that is the only time.
If I do not hit CTRL+C I end up with a portage database that is old. Iamben on IRC tried to establish earlier today why portage would do this.
To which I answer, I still don't know.
Anyway, I configured my server to build a binary of libpcre, and then asked the client to emerge.
Again, the client wanted for "perform a global update" and displayed the output as above, except this time I did not stop it.
i.e. Hit CTRL+C.
I let it do its thing, and then it pulled over the binary libpcre from the server.
Now it looks like it can build GCC-4.5.4 without complaining about C being unable to compile executables.
It is in the middle of building GCC just now, (not as a binary).
I should know in the next hour or so if it is finished.
I'll keep y'es posted._________________Whatever you do, do it properly!

If postage is giving that output over and over, its not being saved. Is something read only that should be read/write?

Since setting up my NFS server to build binaries (which was just 30 minutes ago), portage has stopped repeating the
output. It looks as if it has been written to database this time.
Seems getting the lbpcre back in working order has been the key to all of this.
Now portage is working again._________________Whatever you do, do it properly!

Yes, a think its a good idea to have a server in yer home network, especially if all yer systems are running Gentoo.
Then at least ye can lend a helping hand when times are tough._________________Whatever you do, do it properly!

haha, I'm a student and have no income just now.
It's an old Pentium 4 box with 1.5Gb of Ram, and a few 250Gb disks.
It hosts time and portage to my client, as well as hosting all of my backups.
When it is sitting doing nothing it crunches work units for BOINC.
It's on 24/7 and has been for about 3 years. It's a happy wee box / tower. lol._________________Whatever you do, do it properly!

haha, I'm a student and have no income just now.
It's an old Pentium 4 box with 1.5Gb of Ram, and a few 250Gb disks.
It hosts time and portage to my client, as well as hosting all of my backups.
When it is sitting doing nothing it crunches work units for BOINC.
It's on 24/7 and has been for about 3 years. It's a happy wee box / tower. lol.

For me, it was a spend to save thing. I was running 4 PC 24/7, down from 14 in the days of seti@home classic.
I worked out that 4VMs on modern hardware would save me £40/month off the electric bill. That would have been a payback time of 4 months if I had not suffed it fullof RAM and 2TB WD Greens.

The latter was a bad decision. Two failed after 9 months. Its still only 60W working hard. Each PC was more than that before._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

That was a wise move with regards to moving all your BOINC units to VM. Something which I had never considered.
I suppose if I had the income I would switch to running a similar network.
The box I am running as a "server" just now would not be able to run a VM for Gentoo, and a seperate VM for say Windows crunching BOINC.
It is just an old Pentium 4 processor, and would probably grind to a halt if I tried such a thing.
Incidentaly, many thanks for your help on the IRC yesterday afternoon.
I was a little bit stumped as to what to do when pulling in the packages from Tinderbox, as I could not call emerge to do it's thing.
Got there in the end once I managed to reinstall libpcre._________________Whatever you do, do it properly!