LFS commands, backslashed line continuations, and fileutils

Erika Pacholleck pchllck at nexgo.de
Sat Apr 19 07:54:32 PDT 2003

[19.04.2003] Michael A. Peters <-- :
> On Sat, 2003-04-19 at 03:13, Kelledin wrote:
> > Lately, I'm frequently seeing a lot of people having problems 
> > with certain Ch5 LFS packages (notably fileutils), where static 
> > linking doesn't occur like it should.  Of course, these people 
> > are positive they've followed the book to the letter, normally 
> > because they cut-and-paste the commands with their mouse.
> > 
> > I'm betting that when these unfortunate souls cut-n-paste the 
> > commands, the CnP operation is putting whitespace after the 
> > backslash in LDFLAGS=-static.
> I bet you are right.
> As far as suggestions go - leave the lfs book the way it is (imho) but
> put this in the beginning of the book.
> Perhaps someone should try just to see if this is the case ...

At least in my versions of the books, introduction text always said
to type as seen, and not to copy and paste as not seen.

But maybe it will in future need another remark for those who use
the book: avoid slipping over the border of the page when using a
line scanner ;)
Erika ...---...: pacholleck at nexgo dot de
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message

More information about the lfs-dev mailing list