r3881 - jhalfs/trunk/BLFS/xsl

Roger Koehler roger.o.koehler at gmail.com
Wed Dec 7 05:35:30 PST 2016

On Wed, Dec 7, 2016 at 1:33 AM, Pierre Labastie <pierre.labastie at neuf.fr> wrote:
> On 07/12/2016 00:09, Roger Koehler wrote:
>> On Tue, Dec 6, 2016 at 3:56 PM, Roger Koehler <roger.o.koehler at gmail.com>
>> wrote:
>>> On Sat, Dec 3, 2016 at 11:22 AM,  <pierre at higgs.linuxfromscratch.org>
>>> wrote:
>>>> Author: pierre
>>>> Date: Sat Dec  3 10:22:50 2016
>>>> New Revision: 3881
>>>> Log:
>>>> Fix dependencies when there is
>>>> a <phrase> tag above the <xref>
>>>> Modified:
>>>>     jhalfs/trunk/BLFS/xsl/gen_pkg_list.xsl
>>>> Modified: jhalfs/trunk/BLFS/xsl/gen_pkg_list.xsl
>>> I now get this error message when building a new system with jhalfs
>>> after completing LFS and going on to BLFS:
>>> make: xsltproc: Command not found
>> Once I manually install libxml2 and libxslt, I can proceed with 'make'
>> in /blfs_root/work.
> Hi Roger,
> The change to gen_pkg_list.xsl was really cosmetic, and normally, it is not
> used at all in a jhalfs build. I may have introduced a bug, though, but it
> must be rather subtle. Can you tell me more about what you do exactly, and
> where exactly the error occurs? For example:
> - Which blfs tools you include (blfs-tools dependencies)
> - Does the error occur when building the blfs-tools, or after, when you
> begin building blfs packages?
> Normally, the layout of the Makefile in /blfs_root/work is:
> all : target1 target2 [...] update
> target1:
> <instructions not using xsltproc>
> target2:
> <instructions not using xsltproc>
> [...]
> update:
> <instructions _using_ xsltproc, xmllint, and docbook' dtd>
> So this means that if libxslt, docbook, and libxml2 are not amongst the
> targetN's, the update target will fail. can you check that there are lines
> beginning with xxx-z-target: in the Makefile, where xxx is a 3-digit number
> and target is one of the above?

Thanks, Pierre. I selected all of the blfs_tools as I normally do and
set jhalfs to run the makefile. The first one to run after LFS was
complete was 002-z-OpenSSL, and this is where the error occurred. I
didn't attempt to debug the problem. I just build xsltproc manually,
entered chroot manually, and then ran 'make' in /blfs_root/work, and
everything proceeded as normal. This may be the first time that
002-z-OpenSSL was selected to run first due to the new cacerts
dependency. I don't know if that is the issue. I figured it should be
easy enough to duplicate if someone wanted to try to fix it. I
certainly didn't think I would be the only one to experience the
error. Just thought I would point it out.

More information about the alfs-log mailing list