Jeremy Huntwork wrote:
> There is no technical hindrance to bringing in multilib, the changes are
> minimal. The effect is not so minimal. I would like to know people's
> thoughts on how to deal with multilib in LFS. Specifically, how do we
> handle for x86, where multilib is not an option? Do we just have a note
> that says 'for 64-bit architectures only'? If so, how do we handle this
> in jhalfs?
>
I personally would like to see multi-lib in the book, simply for the
educational value. I figure now is as good a time as any. Having not
done it myself, makes the topic a little difficult. Just taking a
cursory glance at the instructions, it looks as though almost all
instructions are identical for pure64 and 32bit builds. Thinking of
jhalfs here, is it possible to add an additional attribute to the
command tags? For instance, now we have something like (using configure
as an example value for remap):
[command remap="configure"]...[/command]
I don't know if it is legal to do something like:
[command remap="configure" buildtype="{pure|multilib|<null>}"]...[/command]
Or, would new remap parameters have to be added for configure-pure and
configure-multi, where plain configure is for everybody (like old grub
that only builds 32bit).
From a book perspective, it's not a big deal IMO to do one {sect2} with
'pure' commands and another with multi-lib commands...just add a
standard blob (xi) to prefix each section of instructions.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
