Re: commit 8a796f8f is breaking a usecase

"Zhang Wen" ([email protected] via alfs-discuss Mailing List) <[email protected]> Mon, 15 Dec 2025 23:59:24 +0800
Newsgroups gmane.linux.lfs.automated
Message-ID <CAKjfnjq53s=6RLymxUBAjcA=i=hxQTfGGbugqOH7f=psfxTaHw@mail.gmail.com>
Pierre Labastie <[email protected]>
于2025年12月15日周一 21:02写道:
>
> Now, if you insist on keeping your use case (I am not sure why you do
> not want to build the BLFS tools during the first run, maybe you can
> elaborate on this), I think it is better to not generate the non useful
> targets if they are not needed. I'll look at this.
>
> Regards
> Pierre
> --
> http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
> Unsubscribe: See the above information page

I used to build the BLFS tools during the first run, then after the libxml2
package is updated in the BLFS book, I tried to install the latest BLFS
packages with jhalfs on the target system. Some packages linked to libxml2
version A, others linked to libxml2 version B. Then the system is broken.
So I always keep an "pure" system by hand. I always install the ccache package
on a copy of the "pure" system, that speeds up building packages greatly,
and build the blfs tools and the custom tools with jhalfs on the host system,
and then everything all over to update my system, as mentioned on the
chapter 8.2.2.1 of the LFS book.
I know it's my problem that i do not really know how packages depend on each
other, it is ok to me if this approach will not be supported by the
jhalfs project.
Just to elaborate what i'm doing.

-- 
Key fingerprint:
419F 72F3 F3A9 36EE 1B72  B00B C1C3 4BD4 FDA3 362F

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