Re: portability of build?

Am 10.03.25 um 11:11 schrieb Xi Ruoyao ([email protected] via
lfs-support Mailing List):
> On Mon, 2025-03-10 at 11:05 +0100, Rainer Fiebig wrote:
>> Am 09.03.25 um 04:31 schrieb Xi Ruoyao ([email protected] via
>> lfs-support Mailing List):
>>> On Sat, 2025-03-08 at 20:40 +0100, Thomas Seeling wrote:
>>>
>>> /* snip (*/
>>>
>>>> I wanted to install additional software like grub for UEFI, unzip and 
>>>> nfs-utils (with dependencies) and I noticed 2 problems: gcc stops 
>>>> compiling unzip source code with "illegal opcode".
>>>
>>> It's because GMP was built with optimizations specifically to the
>>> current processor.
>>>
>>> The book clearly says:
>>>
>>>    The default settings of GMP produce libraries optimized for the host
>>>    processor. If libraries suitable for processors less capable than the
>>>    host's CPU are desired, generic libraries can be created by appending
>>>    the --host=none-linux-gnu option to the configure command.
>>>
>>>
>>> Please don't skip any book text.  We don't add a paragraph of text into
>>> the book for no reason.
>> Please, show some lenience.  Transferring a system to another machine
>> probably comes long after the initial build and notes on libffi and gmp
>> might be forgotten at that point.  But perhaps it might help to
>> explicitly mention libffi and gmp (and Qt?) in the note in ch. "8.2.3.
>> Deploying LFS on Multiple Systems".
> 
> I've already done it for libffi and gmp in the development book.  For Qt
> I'm not sure and I'm also unsure if there are more cases in BLFS.
Thanks.  Probably better to leave Qt out at that point.  The Qt-chapter
in BLFS would be a better place for a note but I don't have a suggestion
for it yet.

Rainer

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page