i386 -> i686

[Tuinslak]

Hi,

I need to manage a gentoo server in a datacenter for a customer of mine. An other host installed Gentoo on it. Now it seems that the installation hasn't been done as supposed.
It's a sempron cpu and everything has been compiled for i386.

So;

I re-bootstrapped everything, emerge -e system, ran fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu, and gcc-config i686-pc-linux-gnu-3.3.6.

Now

1) is there a way to see if everything has been recompiled for 686?
2) is everything compiling the right way, and not 386?
3) apache errors, is this a gcc/cflag problem?
checking for i686-pc-linux-gnu-gcc... i386-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
It also tells me to check config.log, but I can't find any config.log.. (updatedb && locate config.log .. )


Other problem:
Linux idefix 2.6.12-gentoo-r10 #2 SMP Mon Oct 3 03:14:29 Local time zone must be set--see zic m i686 AMD Sempron(tm) 2800+ AuthenticAMD GNU/Linux

A bad kernel (smp...) with time zone unset. I've created (linked actually) /etc/localtime. Is that enough? To get the message away, do I need to reboot or recompile the kernel?


MySQL has been (badly?) installed. I'd like to remove EVERYTHING from MySQL, and reinstall it, as if it was the very first time I install MySQL (need to set root pass, etc). Any idea how?

Thanks


The make.conf file (partially):
CFLAGS="-march=athlon-xp -O2 -pipe"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
_________________
Tuinslak

[yabbadabbadont]

Assuming your toolchain is now i686, you probably should do an emerge -e world too.

I think that the kernel has to be recompiled after you change the timezone setting to get it to show up correctly.

I don't know about your other issues, sorry.

[Tuinslak]

Emerge -e world has been done.


and how to be sure about the toolchain? That it's set correctly?


emerge apache also doesn't errror anymore.
_________________
Tuinslak

[Bob P]

if you search the forums, you'll find plenty of threads about the trouble that results from attempting to change a CHOST specification. without going into alot of detail about why, yoiu have to do this: