Hello... I'm not the only one with this problem... See these threads in the Gentoo forums.. http://forums.gentoo.org/viewtopic.php?t=12063 http://forums.gentoo.org/viewtopic.php?t=12098 Apparently... some people... including me... are getting these errors while bootstraping on Durons/T-birds... using the -fomit-frame-pinter flag... checking size of char... configure: error: can not run test program while cross compiling Configure in /var/tmp/portage/gcc-3.2/work/build/fastjar failed, exiting. I'm not getting this error when i leave out -fomit-frame-pointer.. The CFLAGS i used that made the bootstrap successful were: CFLAGS="-march=athlon -O3 -pipe" The CFLAGS which caused the bootstrap to fail were: CFLAGS="-march=athlon -O3 -pipe -fomit-frame-pointer"
the solution is to not use -fomit-frame-pointer as you can imagine, there a dozens of gcc optimization flags a user could add to CFLAGS in make.conf. some of them can cause some packages to fail, broken code at run time etc. then if you consider the number of permutations of that set of options, if would be quite a task to maintain an ebuild. so generally, gentoo devs (as far as i know) will support only the default examples given in make.conf. ie. -march=, -mcpu= and an optimization flag, -O3. anything beyond that is really the domain of the individual user.
okay... thanks... that's what i'll do..
Just a notice, but we have a 'flag-o-matic' eclass, that filters out flags.. I think it's best to filter out known bad flags for an ebuild, so it increases the overall stability of the systems.. -fomit-frame-pointer is a heavily used flag, so it would be cool to make it work perfectly in the entire system.
okay i see this was already done
