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.
