Compile of current trunk failing - asan reconfigure

Compile of current trunk failing - asan reconfigure

[Lars Gullik Bjønnes]

With current trunk I have this problem. This was introduced when the
asan was merged into trunk. I thought that I should not have to rebuild
any of the configuration files?

I am building like this:

$ cd gcc-trunk
$ svn update
At revision 193528.
$ cd ..
$ mkdir gcc-build
$ cd gcc-build
$ ../gcc-trunk/configure --prefix=/opt/gcc/gcc-trunk --enable-threads=posix --enable-checking=release --enable-languages=c,c++,lto
$ make -j8


make[6]: Entering directory `/home/lgb/Development/gcc/gcc-build/x86_64-unknown-linux-gnu/32/libsanitizer'
CDPATH="${ZSH_VERSION+.}:" && cd ../../../../gcc-trunk/libsanitizer && /bin/sh /home/lgb/Development/gcc/gcc-trunk/missing --run autoconf
 cd ../../../../gcc-trunk/libsanitizer && /bin/sh /home/lgb/Development/gcc/gcc-trunk/missing --run automake-1.11 --foreign
aclocal.m4:16: warning: this file was generated for autoconf 2.64.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
configure.ac:5: error: Please use exactly Autoconf 2.64 instead of 2.68.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:5: the top level
autom4te: m4 failed with exit status: 1
make[6]: *** [../../../../gcc-trunk/libsanitizer/configure] Error 1
aclocal.m4:16: warning: this file was generated for autoconf 2.64.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
configure.ac:5: error: Please use exactly Autoconf 2.64 instead of 2.68.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:5: the top level
autom4te: m4 failed with exit status: 1
automake-1.11: autoconf failed with exit status: 1
make[6]: *** [../../../../gcc-trunk/libsanitizer/Makefile.in] Error 1

-- 
	Lgb

Re: Compile of current trunk failing - asan reconfigure

[Jonathan Wakely]

On 15 November 2012 08:31, Lars Gullik Bjønnes wrote:
>
> With current trunk I have this problem. This was introduced when the
> asan was merged into trunk. I thought that I should not have to rebuild
> any of the configuration files?

Right, if you haven't modified them you shouldn't need to regenerate them.

I get the same failure on gcc20.

I "solved" it with --disable-libsanitizer, but that's not a real solution.

Re: Compile of current trunk failing - asan reconfigure

[Markus Trippelsdorf]

On 2012.11.15 at 09:48 +0000, Jonathan Wakely wrote:
> On 15 November 2012 08:31, Lars Gullik Bjønnes wrote:
> >
> > With current trunk I have this problem. This was introduced when the
> > asan was merged into trunk. I thought that I should not have to rebuild
> > any of the configuration files?
> 
> Right, if you haven't modified them you shouldn't need to regenerate them.
> 
> I get the same failure on gcc20.
> 
> I "solved" it with --disable-libsanitizer, but that's not a real solution.

As I wrote in the gcc-patches thread, someone has to do the following:

With the right autotools installed locally, running:

ACLOCAL='aclocal -I .. -I ../config' autoreconf -v && rm -fr autom4te.cache

in gcc/libsanitizer and committing the diff should fix the issue.

-- 
Markus

Re: Compile of current trunk failing - asan reconfigure

[Jonathan Wakely]

On 15 November 2012 10:13, Markus Trippelsdorf wrote:
> On 2012.11.15 at 09:48 +0000, Jonathan Wakely wrote:
>> On 15 November 2012 08:31, Lars Gullik Bjønnes wrote:
>> >
>> > With current trunk I have this problem. This was introduced when the
>> > asan was merged into trunk. I thought that I should not have to rebuild
>> > any of the configuration files?
>>
>> Right, if you haven't modified them you shouldn't need to regenerate them.
>>
>> I get the same failure on gcc20.
>>
>> I "solved" it with --disable-libsanitizer, but that's not a real solution.
>
> As I wrote in the gcc-patches thread, someone has to do the following:
>
> With the right autotools installed locally, running:
>
> ACLOCAL='aclocal -I .. -I ../config' autoreconf -v && rm -fr autom4te.cache
>
> in gcc/libsanitizer and committing the diff should fix the issue.

Yep, I'll do it in about 12 hours if it's still broken, but can't do it sooner.

Re: Compile of current trunk failing - asan reconfigure

[Markus Trippelsdorf]

On 2012.11.15 at 10:25 +0000, Jonathan Wakely wrote:
> On 15 November 2012 10:13, Markus Trippelsdorf wrote:
> > On 2012.11.15 at 09:48 +0000, Jonathan Wakely wrote:
> >> On 15 November 2012 08:31, Lars Gullik Bjønnes wrote:
> >> >
> >> > With current trunk I have this problem. This was introduced when the
> >> > asan was merged into trunk. I thought that I should not have to rebuild
> >> > any of the configuration files?
> >>
> >> Right, if you haven't modified them you shouldn't need to regenerate them.
> >>
> >> I get the same failure on gcc20.
> >>
> >> I "solved" it with --disable-libsanitizer, but that's not a real solution.
> >
> > As I wrote in the gcc-patches thread, someone has to do the following:
> >
> > With the right autotools installed locally, running:
> >
> > ACLOCAL='aclocal -I .. -I ../config' autoreconf -v && rm -fr autom4te.cache
> >
> > in gcc/libsanitizer and committing the diff should fix the issue.
> 
> Yep, I'll do it in about 12 hours if it's still broken, but can't do it sooner.

Well, it turned out that "./contrib/gcc_update --touch" is enough to fix
the issue.

-- 
Markus