[lfs-support] Ensuring a generic x86_64 build

Paul Rogers paulgrogers at fastmail.fm
Mon Sep 18 15:20:02 PDT 2017

> I noticed this note about GMP:
> "The default settings of GMP produce libraries optimized for the host
> processor."
> Using the default configure settings in the summary of build options I
> see "Host type: skylake-pc-linux-gnu".  I then see gcc is using
> "-mtune=skylake" when compiling the GMP library.  Now if I use
> configfsf.guess as mentioned in the LFS book, it will build with "Host
> type: x86_64-pc-linux-gnu".  So I've made a note to recompile GMP when
> I move it to the older system.

Isn't that a PITA?  But check out the "fat" option.

> Beyond GMP, is anyone aware of other LFS packages which, when using
> the default compilation options, could lead to binaries that are
> tightly coupled to the host build's processor?  I'd like my build to
> be as generic as possible so that it can run on any other x86_64
> system.

I do too, just got into trouble over this and had to rebuild. 
Apparently that is the only package (so far!) to be so presumptuous.

More information about the lfs-support mailing list