to my CFLAGS in /etc/make.conf. I did this, but noticed that portage was still using some very basic CFLAGS, not the ones I had specified. I did some digging and found a line

Code:

strip-flags

in my /usr/portage/sys-devel/gcc/gcc-3.2.3-r3.ebuild file. The comments in the file instructed that this line should be left un-commented, but I wanted my CFLAGS to be used, so I commented this line out.

Now gcc has compiled itself correctly, as well as ttmkfdir and XFree, and I am on step 51 of 300 in my emerge -e world. I'm timing it as well, so this should be interesting. 3 hours down..... who knows how many more to go......

Let me know if this helps anybody out! Gentoo/Linux user for 3 weeks now and one step further from n00b status.

Sound neat , I've had some similiar problems myself. I don't want to sound negative, but I just wonder, what could happen when removing that strip-flags line? I mean, the developers have put it there for some reason. Have you experienced any trouble yet?_________________Physics is like sex: sure, it may give some practical results, but that's not why we do it.
--Richard Feynman

so far everything has compiled correctly, or at least it was when i last checked it 3 hours ago. I'm sure that the line has some purpose, as you said, but i'm not sure what it is, and i'm even less sure why removing that line improves the performance of the compilation. give it a try, and i hope it works as well for you!

OK, I hope you will be successful!
I will however not upgrade right now. I was doing it, but when the problems emerged (instead of the ebuild ) and I started to dig in the mess, I realized I was just switching from gcc-*-r(n) to gcc-*-r(n+1) where 1<n<10. I won't go through this process until it at least looks like a cool thing to do

But I will keep your solution in mind!_________________Physics is like sex: sure, it may give some practical results, but that's not why we do it.
--Richard Feynman

when strip-flags is in an ebuild, then the ebuild will use the cflags provided by the maintainer of the soucecode instead of the cflags you have in your make.conf.

its a REALLY bad idea to remove strip-flags from an ebuild, because if you got some really hardcore-code-killing cflags, and you compile GCC with them (if it completes.), then you will have a b0rked box_________________Encrypt, lock up everything and duct tape the rest