Progress: I've discovered that athlon64 is a valid gcc make flag, so I changed it back.
I've also discovered that the /etc/make.profile symlink was pointing at the x86 default-linux profile set, not the amd64 profile. I'm attempting a recompile now with the symlink changed, and hopefully this will fix my problems. I wonder if this latent error is not about to cost me a whole bunch more though. Is there anything I should do with the emerge command or any other command in order to correct this profile problem? Thanks Jeff On Sunday 14 December 2008 09:17:22 pm Jeff Cranmer wrote: > Thanks, > > That only adds more questions. > My environment is amd64. It appears to have downloaded the i586 binary. > Surely this is incorrect? > > my make.conf file contains the line > CFLAGS="-O2 -pipe -march=athlon-xp", which should trigger the 64 bit > binaries to be downloaded and acted upon. > > The CFLAGS variable was previously set to "-O2 -pipe -march=athlon64", and > I don't think that athlon64 is a valid gcc compile flag, but the response > was the same with this set of CFLAGS variables too. > > Also,since I changed the CFLAGS variable, is there anything I need to do in > compilation to correct any errors resulting from the original (I believe > invalid) variable? > > Any suggestions gratefully received. > > Jeff > > On Saturday 13 December 2008 06:43:24 pm Jean-Baptiste Mestelan wrote: > > 2008/12/13 Jeff Cranmer <jcranme...@earthlink.net> > > > > > Perhaps it would have done if I knew where the download page was. > > > > The file /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0.11.ebuild > > will disclose this information, and hints at > > https://jdk-distros.dev.java.net/developer.html > > > > > > Regards.
