On 8/2/2011, at 9:11pm, Nils Holland wrote: > On 12:41 Tue 08 Feb , Stroller wrote: > >> If my process wasn't clear from my last email: it looks like, following that >> document, you have to do the whole thing with changed CHOST, *before* making >> any changes to CFLAGS. It appears like only after you've `emerge -e world` >> with the new CHOST can you change CFLAGS. > > Thanks for the hint, right now I've got the i486 stage3 in a chroot > and have changed both the CHOST and CFLAGS to i586. If that leads to > problems, as you've described, I'll start over with only setting CHOST > to i586 at first and then changing CFLAGS. Currently the build process > is running fine, however, but I'm mentally prepared for difficults > now. ;-)
I completed the `emerge -e world` with the new CHOST, ran `lafilefixer --justfixit && revdep-rebuild` and then Python and the Perl packages, as listed in the documentation. I'm pretty sure I ran `lafilefixer --justfixit && revdep-rebuild` again, finding nothing. Changing CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer" failed again on the first package, ncurses. CFLAGS="-mtune=native -O2 -pipe -fomit-frame-pointer" seems to be working (now on package 10 of 155). Perhaps I should have tried CFLAGS="-O2 -march=i586 -pipe" instead. I don't really know what the "-fomit-frame-pointer" part does - I imagine someone suggested it, perhaps on here, years ago, and it has got copied from system to system. Stroller.
