On 3/19/11 5:52 PM, Zeev Tarantov wrote:
> On Sat, Mar 19, 2011 at 21:33, Chet Ramey <chet.ra...@case.edu> wrote:
>> On 3/18/11 9:42 PM, Zeev Tarantov wrote:
>>
>>> x86_64-pc-linux-gnu-gcc: error: \: No such file or directory
>>> x86_64-pc-linux-gnu-gcc: error: \: No such file or directory
>>> x86_64-pc-linux-gnu-gcc: error: \: No such file or directory
>>> x86_64-pc-linux-gnu-gcc: error: \: No such file or directory
>>> lto-wrapper:
>>> /usr/x86_64-pc-linux-gnu/gcc-bin/4.6.0-pre9999/x86_64-pc-linux-gnu-gcc
>>> returned 1 exit status
>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre9999/../../../../x86_64-pc-linux-gnu/bin/ld:
>>> lto-wrapper failed
>>
>> It would be helpful to see the exact command that caused this error, in
>> its unexpanded state.
>
> I'm sorry, I do not understand you.
> The lines immediately preceding the lines you have quoted are the command.
Yeah, like I said, I figured it had to be a shell script. There has to
be something that is transforming the command before it's eventually
executed. It might be the effect of the -flto option; it might not.
Either way, I can't see how it's a bash bug at this point.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
