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
