Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Matt Burgess
On Fri, 2012-02-17 at 23:55 +0100, Pierre Labastie wrote: > 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

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Pierre Labastie
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 >> d

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Pierre Labastie
Le 17/02/2012 23:08, Thomas Pegg a écrit : > After looking at this all that is needed is to add the following line > to common/libs/func_book_parser right after we check out the sources. > > cd ${PROGNAME}-$LFSVRS; bash process-scripts.sh>> $LOGDIR/$LOG 2>&1 ; cd .. > > This quells all those messa

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Bruce Dubbs
Thomas Pegg wrote: > cd ${PROGNAME}-$LFSVRS; bash process-scripts.sh >> $LOGDIR/$LOG 2>&1 ; cd .. May I suggest: pushd ${PROGNAME}-$LFSVRS; ...; popd It's a little more robust. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubs

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Bruce Dubbs
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 u

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Thomas Pegg
On Fri, Feb 17, 2012 at 4:59 PM, Pierre Labastie wrote: > Le 17/02/2012 18:30, Bruce Dubbs a écrit : >> Matthew Burgess wrote: >> >>> I had a quick look at the Makefile and make-aux-files.sh script and couldn't >>> see why that line is required.  Bruce, is there a reason those .script >>> files a

Re: [blfs-dev] Git-1.7.9 issues

2012-02-17 Thread Andrew Benton
On Fri, 17 Feb 2012 19:50:51 +0200 Thanos Baloukas wrote: > Hello everybody > I just subscribed on this list. I hope I can help. > > The book states python-2.7.2 as required dependency. I'm not sure if the > INSTALL source tree's file is up to date, but it says nothing about > python. Except z

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Pierre Labastie
Le 17/02/2012 18:30, Bruce Dubbs a écrit : > Matthew Burgess wrote: > >> I had a quick look at the Makefile and make-aux-files.sh script and couldn't >> see why that line is required. Bruce, is there a reason those .script files >> are >> deleted? > It's cleanup. For jhalfs, it would be better i

[blfs-dev] Git-1.7.9 issues

2012-02-17 Thread Thanos Baloukas
Hello everybody I just subscribed on this list. I hope I can help. The book states python-2.7.2 as required dependency. I'm not sure if the INSTALL source tree's file is up to date, but it says nothing about python. Except zlib that is in LFS, it states ssh, Perl, openssl, libcurl, expat, Tcl/T

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Bruce Dubbs
Matthew Burgess wrote: > I had a quick look at the Makefile and make-aux-files.sh script and couldn't > see why that line is required. Bruce, is there a reason those .script files > are > deleted? It's cleanup. For jhalfs, it would be better if a different set of rules were used if different

Re: [lfs-dev] jhalfs's error log

2012-02-17 Thread Matthew Burgess
On Fri, 17 Feb 2012 10:30:06 +0100, Pierre Labastie wrote: > Le 17/02/2012 07:37, xinglp a écrit : >> This is the log produced by jhalfs, some errors in it, but it worked >> well when build lfs. > Thanks for the report. I knew that, but the reason is outside > jhalfs. It is in the Makefile of the