[alfs-discuss] [lfs-dev] Searching for a chapter on multilib

Pierre Labastie pierre.labastie at neuf.fr
Sun Jul 21 09:40:11 PDT 2019

On 13/07/2019 08:43, DJ Lucas wrote:
> On 7/12/2019 5:53 PM, DJ Lucas via lfs-dev wrote:
>> I did have a patch for jhalfs that was relatively simple for Thomas's build,
>> but it's went away with last cleanup, but was not difficult. I think all I
>> had to do was to expand the glibc-* target 
> I had to add -32 to the sed for the package titles to extract the package name.
>> so that the multiple builds were possible, but with the multiple copies of
>> the book, amd64+i686/x32, it has to be expanded again to cope. I'll take a
>> stab at adding it back this weekend if somebody else hasn't already.
> The additional options aren't so easy as I would have had to modify lfs.xsl
> extensively to account for all of the arch= parts. Ultimately, I changed the
> method used to extract commands to a profiled two pass of xsltproc (as is
> already done with the books themselves). I'm going to suggest this to Pierre
> when he gets back as it'll ultimately simply lfs.xsl, removing 20 unneeded
> lines, 6 of which are an entire xsl:select on sect1). I did not do this for
> the chapter03.xml (for the tarballs) in LFS, just left a FIXME in there
> temporarily. Also, I do not know if it is possible to test for a specific
> value of BRANCH="branch-multilib" to further limit the unneeded options (I
> can't really do anything about WORKING_COPY -- the option needs to be there as
> we have no idea what is going on with a local copy).
> Anyway, see attached.

Created ticket #1722 for alfs, so that I do not forget...


More information about the alfs-discuss mailing list