configure fails with gcc 4.6.0 LTO
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' -DSTANDARD_UTILS_PATH='/bin:/usr/bin:/sbin:/usr/sbin' -DSYS_BASHRC='/etc/bash/bashrc' -DSYS_BASH_LOGOUT='/etc/bash/bash_logout' -DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -g -O2 -pipe -march=core2 -mcx16 -msahf --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=4096 -mtune=core2 -fexcess-precision=fast -Wno-unused-result uname output: Linux wolfpc 2.6.38 #16 SMP PREEMPT Fri Mar 18 13:12:51 IST 2011 x86_64 Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: 4.2 Patch Level: 8 Release Status: release Description: pre-release gcc and pre-release binutils, Link Time Optimization enabled. GNU ld (Linux/GNU Binutils) 2.21.51.0.7.20110306 from config.log: configure:3077: $? = 0 configure:3084: x86_64-pc-linux-gnu-gcc -v >&5 Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.0-pre/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.6.0-pre/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /home/system/var_tmp_portage/portage/sys-devel/gcc-4.6.0_pre/work/gcc-4.6.0-/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.0-pre --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.6.0-pre --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.6.0-pre/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.6.0-pre/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --with-ppl --with-cloog --disable-ppl-version-check --with-cloog-include=/usr/include/cloog-ppl --enable-lto --disable-nls --with-system-zlib --disable-werror --enable-secureplt --enable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --enable-cld --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.6.0-pre/python --enable-checking=release --enable-languages=c,c++,java,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo SVN' Thread model: posix gcc version 4.6.0-pre 20110318 (prerelease) rev. 171169 (Gentoo SVN) configure:3088: $? = 0 configure:3095: x86_64-pc-linux-gnu-gcc -V >&5 x86_64-pc-linux-gnu-gcc: error: unrecognized option '-V' x86_64-pc-linux-gnu-gcc: fatal error: no input files compilation terminated. configure:3099: $? = 1 configure:3122: checking for C compiler default output file name configure:3144: x86_64-pc-linux-gnu-gcc -g -O2 -pipe -march=core2 -mcx16 -msahf --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=4096 -mtune=core2 -fexcess-precision=fast -Wno-unused-result -flto -DDEFAULT_PATH_VALUE='"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"' -DSTANDARD_UTILS_PATH='"/bin:/usr/bin:/sbin:/usr/sbin"' -DSYS_BASHRC='"/etc/bash/bashrc"' -DSYS_BASH_LOGOUT='"/etc/bash/bash_logout"' -DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -Wl,-O1 -Wl,--as-needed -Wl,-O1 -flto conftest.c >&5 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-pre/x86_64-pc-linux-gnu-gcc returned 1 exit status /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../x86_64-pc-linux-gnu/bin/ld: lto-wrapper failed collect2: ld returned 1 exit status configure:3148: $? = 1 configure:3186: result: configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "bash" | #define PACKAGE_TARNAME "bash" | #define PACKAGE_VERSION "4.2-release" | #define PACKAGE_STRING "bash 4.2-release" | #define PACKAGE_BUGREPORT "bug-bash@gnu.org" | #define ALIAS 1 | #define PUSHD_AND_POPD 1 | #define RESTRICTED_SHELL 1 | #define PROCESS_SUBSTITUTION 1 | #define PROMPT_STRING_DECODE 1 | #define SELECT_COMMAND 1 | #define HELP_BUILTIN 1 | #define ARRAY_VARS 1 | #define DPAREN_ARITHMETIC 1 | #define BRACE_EXPANSION 1 | #define COMMAND_TIMING 1 | #define EXTENDED_GLOB 1 | #define EXTGLOB_DEFAULT 0 | #define COND_COMMAND 1 | #define COND_REGEXP 1 | #define COPROCESS_SUPPORT 1 | #define ARITH_FOR_COMMAND 1 | #define NETWORK_REDIRECTIONS 1 | #define PROGRAMMABLE_COMPLETION 1 | #define DEBUGGER 1 | #define CASEMOD_ATTRS 1 | #define
Re: configure fails with gcc 4.6.0 LTO
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-pre/x86_64-pc-linux-gnu-gcc > returned 1 exit status > /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../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. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: configure fails with gcc 4.6.0 LTO
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-pre/x86_64-pc-linux-gnu-gcc > > returned 1 exit status > > /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../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. -mike signature.asc Description: This is a digitally signed message part.
Re: configure fails with gcc 4.6.0 LTO
On Sat, Mar 19, 2011 at 21:33, 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-pre/x86_64-pc-linux-gnu-gcc
>> returned 1 exit status
>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../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.
Configure was invoked this way:
generated by GNU Autoconf 2.63. Invocation command line was
$ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --libdir=/usr/lib64 --without-afs
--enable-net-redirections --disable-profiling --disable-mem-scramble
--without-bash-malloc --without-installed-readline --disable-nls
--with-curses
The only thing that is _relevant_ I think is that gcc 4.6 trunk
invoked with LTO fails configure.
I have just reproduced this with minimal flags ("-g -O2 -flto"):
gcc version 4.6.0-pre 20110319 (prerelease) rev. 171177 (Gentoo SVN)
configure:3088: $? = 0
configure:3095: x86_64-pc-linux-gnu-gcc -V >&5
x86_64-pc-linux-gnu-gcc: error: unrecognized option '-V'
x86_64-pc-linux-gnu-gcc: fatal error: no input files
compilation terminated.
configure:3099: $? = 1
configure:3122: checking for C compiler default output file name
configure:3144: x86_64-pc-linux-gnu-gcc -g -O2 -flto
-DDEFAULT_PATH_VALUE='"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"'
-DSTANDARD_UTILS_PATH='"/bin:/usr/bin:/sbin:/usr/sbin"'
-DSYS_BASHRC='"/etc/bash/bashrc"'
-DSYS_BASH_LOGOUT='"/etc/bash/bash_logout"'
-DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -Wl,-flto
conftest.c >&5
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-pre/x86_64-pc-linux-gnu-gcc
returned 1 exit status
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../x86_64-pc-linux-gnu/bin/ld:
lto-wrapper failed
collect2: ld returned 1 exit status
Are these flags crazy? Am I a ricer now, using "-O2 -g" ?
Mike, is it your opinion that unless I can fix a bug I should not
report it at all? If so, I do not agree. GCC upstream are of the
impression that GCC 4.6 LTO is ready for production use because they
don't know of failures. In the real world, it can't compile most of
the important packages on my system. The discrepancy, as far as I can
tell, is caused by your policy. Drop on GCC the list of 100 gentoo
packages that don't build with 4.6 trunk + LTO. Let them state in
their documentation that the feature is experimental and is not
expected to work.
Re: configure fails with gcc 4.6.0 LTO
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-pre/x86_64-pc-linux-gnu-gcc >>> returned 1 exit status >>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../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, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: configure fails with gcc 4.6.0 LTO
On 3/19/11 5:52 PM, Zeev Tarantov wrote: > On Sat, Mar 19, 2011 at 21:33, 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-pre/x86_64-pc-linux-gnu-gcc >>> returned 1 exit status >>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.0-pre/../../../../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, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
