-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 10 Nov 2007 09:30 in article <[EMAIL PROTECTED]> of linux.gentoo.user, Stefan G. Weichinger([EMAIL PROTECTED]) wrote:
> David W Noon schrieb: > >> You need to consider CHOST as well, to ensure you make the most of >> the newer CPUs. >> >> Here is what I use on an E6600 machine: >> >> CHOST="x86_64-pc-linux-gnu" >> CFLAGS="-march=nocona -mmmx -m3dnow -msse -msse2 -msse3 >> -mfpmath=sse,387 -O2 -pipe" [snip] > Phew, this scares me ;) > > I use > CHOST="i686-pc-linux-gnu" > > now, and don't want to go 64bit anyway (at least not in the near > future), so I think will just edit the CFLAGS for a start and > re-emerge system, then world? I don't understand why one would want to run a 64-bit CPU in 32-bit mode. If you change the CHOST, CFLAGS and CXXFLAGS variables, then do: emerge -e system emerge -e world you will have converted everything except your kernel to 64-bit. This was what you were planning anyway, but the change of CHOST as well will give you a 64-bit toolchain. The only problems will be packages that are stable on x86 but still unstable on amd64 or causing similar problems during rebuild. But these can be skipped by doing: emerge --resume --skipfirst A quick rebuild of the kernel and your system will be wall-to-wall 64-bit and running at maximum speed. I don't see it as a major task, other than waiting for the re-emerge of world to complete, which could take a couple of days. - - -- Regards Dave [RLU#314465] ====================================================== [EMAIL PROTECTED] (David W Noon) ====================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHNb3G9MqaUJQw2MkRAslaAJ9CFAg4waeBPcGIK9tr1HAMVenuRACgpzG/ bFQFgn0ON9FcA8AywEqpoMg= =j25L -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
