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/sha
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
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
> > x8
t-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 (&qu
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-gc
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: