[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: configure fails with gcc 4.6.0 LTO
From: |
Chet Ramey |
Subject: |
Re: configure fails with gcc 4.6.0 LTO |
Date: |
Sat, 19 Mar 2011 18:15:47 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 |
On 3/19/11 5:52 PM, Zeev Tarantov wrote:
> On Sat, Mar 19, 2011 at 21:33, Chet Ramey <chet.ramey@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 chet@case.edu http://cnswww.cns.cwru.edu/~chet/