lfs-4.0 : chroot problem... end ?

Matijs matijs at hotfusion.org
Thu Jan 23 11:22:29 PST 2003


---- Original Message -----
From: "Benoit" <thunderben at free.fr>
To: <lfs-support at linuxfromscratch.org>
Sent: Thursday, January 23, 2003 8:21 PM
Subject: lfs-4.0 : chroot problem... end ?


> Hi,
>
> >> Subsidiary question : what does mean backslashes use in some command ?
> >> example (bash build) :
> >>  ./configure --enable-static-link \
> >>       --prefix=$LFS/static --with-curses &&
> >> make &&
> >> make install
> >>
> >
> > This is probably the root of your problem. The backslash tells the
> >shell that the command is continuing (so you should see the prompt
> >chnage from '$' to '>'). The backslash needs to be the last key on the
> >line, do NOT type any spaces after it before you hit the 'enter' key.
>
> Yeah, this is it ;o)
> So I gonna re-built my static environment from the begining !
>
> But does someone can explain to me the gain of these backslash ?
> What is the difference between :
> "./configure --enable-static-link \
>      --prefix=$LFS/static --with-curses &&
>      ...
> "
>
> and
>
> "./configure --enable-static-link  --prefix=$LFS/static --with-curses &&
..."
>
> ???
>
>
> Thanks to all
> Benoit

Using backslashes makes the commands more readable. There is no difference
between you two examples.

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message



More information about the lfs-support mailing list