John Myers wrote:
On Monday 21 February 2005 08:09, George Roberts wrote:It did turn out to be something borked, I found the link http://gentoo-wiki.com/HOWTO_Migrate_to_GCC_3.4. When I followed the directions there, I ran into the same error messages.
*** Can only configure for one host and one target at a time.
*** Can only configure for one host and one target at a time.
*** Can only configure for one host and one target at a time.
*** Can only configure for one host and one target at a time.
*** Can only configure for one host and one target at a time.
I have searched the posts in here but can not locate anything for either issue, any help would be greatly appreciated.
Seems like your CHOST or something similar may be b0rked. Please run # emerge --info and post the result.
When I checked my make.conf I found:
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer "
CHOST="i686-pc-linux-gnu "
CXXFLAGS="${CFLAGS}".
Humm, maybe a Athlon-xp is not a i686 so I commented out that line. #CHOST="i686-pc-linux-gnu "
Time to test it, emerge --resume. This time no error messages, life is sweet again! Time for bed. When I get up this morning, I checked the versons I now have. # gcc-config -l [1] i686-pc-linux-gnu-3.3.4 * [2] i686-pc-linux-gnu-3.4.3-20050110 [3] i686-pc-linux-gnu-3.4.3-20050110-hardened [4] i686-pc-linux-gnu-3.4.3-20050110-hardenednopie [5] i686-pc-linux-gnu-3.4.3-20050110-hardenednossp
Duh, I've seen that name somewhere before.
As you might notice the gcc-3.3.5-r1 that was giving me the grief is *_not_* in the installed list.
If a Athlon-xp processor is not a i686-pc-linux-gnu, what would be the right setting for the CHOST line of make.conf?
--
[email protected] mailing list
