Robert Mcleod wrote:
> Chris Staub wrote:
>> Robert Mcleod wrote:
>>
>>> <snip>
>>> I followed the book to the letter from what i can tell:
>>> [EMAIL PROTECTED]:/media/sdb3/binutils-build$ CC="gcc -B/usr/bin/"
>>> [EMAIL PROTECTED]:/media/sdb3/binutils-build$ time {
>>> ../binutils-2.17/configure --prefix=/tools --disable-nls
>>> --disable-werror && make && make install }
>>>
>>>
>> The problem is that you split the "CC=" bit apart from the rest of the
>> command. That's supposed to be immediately before the configure command
>> (CC="gcc -B/usr/bin/" ../binutils-2.17/configure...), just as written in
>> the book.
>>
> Thanks for the help, *but* considering that the line CC="gcc
> -B/usr/bin/" is just setting the CC environment variable I don't
> understand why that would make a difference. Am I missing some subtle
> point here? Either way, I did try that and had the same result as the
> first time ("--hash-style" being an unrecognised option of ld).
To amplify what Bauke said in another post...
When a variable is assigned *on the same line* as a following command,
the variable-value pair is *temporarily* exported into the new
environment created in the bash sub-shell that is spawned to execute a
command normally (this can be overridden in various ways) and does *not*
exist in the current shell.
When the variable is defined as you have defined it, it exists in the
current shel, but is not exported. This can be over-ridden by, e.g.
export CC="...."
or after defining it, e.g.
export CC
"Man bash" is your friend here. Been *lots* of changes over the years
*and* every shell is slightly different.
>
> <snip>
HTH
--
Wit
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
