Le 17/02/2012 23:19, Bruce Dubbs a écrit :
> Pierre Labastie wrote:
>
>> jhalfs needs an xml file to process for extracting commands scripts.
>> 'index.xml' in book sources is the most obvious choice. But using this file
>> leads necessary to try to find the '.script' entities, which have been
>> deleted or do not exist.
>> Another choice is to use lfs-full.xml, after 'make validxml'.
>> I am currently testing that, but the target validxml depends on maketar
>> (because aux-file-data;sh does a `ls lfs-bootscript*.bz2') and that is not
>> specified on the 'validxml:' line in Makefile.
>> Maybe one of you could do that (add maketar as a dependency of validxml)
> I can make a special target for you it that makes a difference, but the
> lfs-full.xml should do what you want.  It basically just satisfies all
> the includes and creates one big xml file.  Do you need more than that?
>
> I'm really not sure what the problem is.  The current jhalfs works fine
> for me.
Well, not really a problem with jhalfs. If somebody tries to type
'make validxml' in a just extracted LFS book source
(not needed very often I agree, but this is what I tried before
Thomas gave a smarter solution for jhalfs), it hangs forever:

pierre@turboli:~/downloads/lfsbook$ make validxml
Creating and cleaning /home/pierre/tmp
Processing bootscripts...
Validating the book...
ls: cannot access lfs-bootscripts*.bz2: No such file or directory
[hangs]

The reason is that the line:

validxml: tmpdir (in Makefile)

should be:

validxml: maketar tmpdir

Pierre
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to