On 07/30/2011 06:22 PM, Rob Landley wrote:
> On 07/29/2011 07:29 PM, Randy McMurchy wrote:
>> I am open to suggestions, let the community speak out! C'mon, we need
>> to keep BLFS alive!
>
> So I grabbed the SVN, which produced nothing interesting in the top
> level directory, guessed I wanted "book", there was a readme in there,
> told me I could run make, and I did.  It sat there for three minutes
> "validating the book" before I gave up and killed it.
3 minutes seems excessive. What kind of machine are you building on? My 
dev machine is no speed demon, wouldn't necessarily call it a slouch, 
but a full render of BLFS for distribution takes 1:56 for me.
> Looked at the
> readme some more, it said I could do "make nochunks", which i did, and
> it started validating xml again.  Killed it, opened up the makefile,
> searched for nochunks, it didn't have an obvious dependency on
> validating (oh great, another crawling makefile horror) searched for the
> "Validating the book" string, put an echo in front of its targets, that
> did nothing, searched again and found a SECOND instance of this, put an
> echo in front of THOSE targets, and then make nochunks died with:
>
> Generating profiled XML for XHTML...
> warning: failed to load external entity "tmp/blfs-full.xml"
> unable to parse tmp/blfs-full.xml
> make: *** [tmp/blfs-html.xml] Error 6
>
You broke something in the makefile.
> That was about the limit of my interest for the moment.  I have a guess
> why you have no new developers.
It's good to have a fresh perspective. I mean, I've been working on BLFS 
for 10+ years now, so I know what to expect. But as Bruce said earlier, 
BLFS is a big book. The PDF is what, 1300 pages now? Patience is 
certainly going to be a requirement in its current form.
> Rob
-- DJ Lucas


-- 
This message has been scanned for viruses and
dangerous content, and is believed to be clean.

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

Reply via email to