On Fri, 13 Nov 2020 at 09:29, Kevin Buckley <kevin.m.buck...@gmail.com> wrote: > > Hi Thomas, > > I believe that, as of Revision: 12059, your Zlib section in Chapter 5 > is missing the "--host=$LFS_TGT" flag > > Compare > > <para>Prepare Zlib for compilation:</para> > > <screen><userinput remap="configure">./configure > --prefix=/usr</userinput></screen> > > <para>Compile the package:</para> > > > with the corresponding XML from the GZip section > > > <para>Prepare Gzip for compilation:</para> > > <screen><userinput remap="configure">./configure --prefix=/usr > --host=$LFS_TGT</userinput></screen> > > <para>Compile the package:</para> > > > When I came to build the Zlib, I ended up getting an error from the > host compiler > and it took me a while to work out why the build wasn't using the compiler in > $LFS/tools/bin. > > It is also possible that the 32-bit and x32 build instructions for > Zlib are missing the > $LFS_TGT in their CC configure overrides that ones sees in the Chapter 5 > Ncurses > > zlib.xml:<screen><userinput remap="configure">CC="gcc -m32" \ > zlib.xml:<screen><userinput remap="configure">CC="gcc -mx32" \ > > Cf > > ncurses.xml:<screen><userinput remap="configure">CC="$LFS_TGT-gcc > -m32" \ > ncurses.xml:<screen><userinput remap="configure">CC="$LFS_TGT-gcc > -mx32" \ > > Hoping that helps, and thanks again for the Mulitlib additions, > Kevin
What I have since discovered is that the Configure script for Zlib doesn't accept the --host= argument, hence, I guess, the use of the CC= constructs in the Multilib stanzas. With that in mind, the x86_64 configure probably needs to be marked up as <screen><userinput remap="configure">CC="$LFS_TGT-gcc" \ ./configure --prefix=/usr</userinput></screen> so as to enforce the use of the compiler in /tools/bin. Apologies for any confusion, Kevin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
