On 08/01/2016 13:52, Pierre Labastie wrote:
On 08/01/2016 13:42, Read, James C wrote:
This is wrong: if you enter:
SOMEVAR=xxx <somecommand>
then <somecommand> is executed with SOMEVAR=xxx in its environment, but
SOMEVAR is not set for further commands
So if you enter:
SOMEVAR=xxx && <somecommand>
then <somecommand> knows nothing about SOMEVAR.
You should replace && with \\ in the above part of your script.
Would just deleting the && work?

I do not think so: you either need to put all on one line, eg (the mailer might truncate the line):

CC=$LFS_TGT-gcc AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib ../binutils-2.25.1/configure --prefix=/tools --disable-nls --disable-werror --with-lib-path=/tools/lib --with-sysroot

or use the continuation character \\ as in the book.

Pierre

Ooops sorry, the continuation character is `\' (only one character). Same for my former message.

Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to