Compiler optimization flags in building LFS-5.1.1

Kevin Jordan kmj7777 at
Wed Sep 8 12:17:42 PDT 2004

I wouldn't put optimizations on binutils, gcc, glibc, or grub.  I
forgot once and compiled with optimizations on grub and the hd numbers
turned out strangely (i.e. something like 10604029340 or another
ridiculously large number) and so it wouldn't let me do anything. 
Found out later optimizing it messed it up.  I suppose something like
this would happen for the others that are not recommended you put
flags on.  My flags are "-march=athlon-xp -pipe -fomit-frame-pointer
-msse -mmmx -m3dnow" and have worked well for me.

On Wed,  8 Sep 2004 11:13:51 -0700, LEE,CHRISTIAN WELDON
<clee1750 at> wrote:
> After making my first successful build of LFS-5.1.1 (completely by the
> book) I figured I'd try to redo it, this time optimized for my CPU
> (Athlon XP 1800).
> Have you all had much luck building LFS-5.1.1 with optimization flags set?
> For instance, I used these flags:
> -O3
> -march=athlon-xp
> -msse
> -mfpmath=sse,387
> -fomit-frame-pointer
> -funroll-loops
> -m3dnow
> I got as far as glibc in the temp system (ch 5) before I got an error on
> the make install.
> Has anyone compiled binutils, gcc, and glibc, and grub (and had the
> test-suites run successfully) with these or similar optimizations? Is it
> safe to use optimizations on all of the others that weren't mentioned in
> the book (including the kernel)?
> --
> FAQ:
> Unsubscribe: See the above information page

More information about the lfs-support mailing list