On 3/19/11 5:41 PM, Mike Frysinger wrote:
> On Saturday, March 19, 2011 17:33:36 Chet Ramey 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-linu
>>> x-gnu/bin/ld: lto-wrapper failed
>>
>> It would be helpful to see the exact command that caused this error, in
>> its unexpanded state.
>
> it's right above (this is a snippet from config.log). however, i'm not sure
> looking into this bug report is useful. we already told this guy to stop
> using gcc-4.6 and using ridiculous CFLAGS/LDFLAGS if he wasnt going to assist
> in figuring out the bugs.
I saw the command, but I figured there had to be more to it (e.g., it was
a shell script or something). There's nothing there that contains a
backslash or anything else that might indicate the reason for the error.
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/
