Re: commit 8a796f8f is breaking a usecase
"Pierre Labastie" ([email protected] via alfs-discuss Mailing List) <[email protected]> Sun, 21 Dec 2025 09:26:28 +0100
| Newsgroups | gmane.linux.lfs.automated |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1766305602-26371-51416 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2025-12-15 at 23:59 +0800, Zhang Wen wrote: > Pierre Labastie <[email protected]> > =E4=BA=8E2025=E5=B9=B412=E6=9C=8815=E6=97=A5=E5=91=A8=E4=B8=80 21:02=E5= =86=99=E9=81=93=EF=BC=9A > >=20 > > 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. > >=20 > > Regards > > Pierre > > -- > > http://lists.linuxfromscratch.org/sympa/info/alfs-discuss > > Unsubscribe: See the above information page >=20 > 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. Thanks for the explanation. I think the libxml2 problem has been transient, and that now it is fixed because icu is recommended. Anyway, I have committed a change in the logic (using make conditionals instead of shell ones), so that now, the mk_BLFS_TOOL timestamp is only generated if blfs tools are built. This should fix your problem. I'm sorry I have not been able to test thoroughly, and now I must leave for Christmas vacations. I'll try to monitor the list while away, so please report any problem you may encounter. Pierre ------------=_1766305602-26371-51416 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- http://lists.linuxfromscratch.org/sympa/info/alfs-discuss Unsubscribe: See the above information page ------------=_1766305602-26371-51416--