On 06/30/2015 02:54 PM, Jonathan Wakely wrote: > On 29/06/15 18:57 +0200, Michael Haubenwallner wrote: >> Actually, an unexpected libstdc++-v3/configure change is introduced by some >> inconsistency in >> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=223196 >> where acinclude.m4 contains different code than the recreated configure: >> >> acinclude.m4-3973: case "${target_os}" in >> acinclude.m4#3974: gnu* | linux* | solaris*) >> acinclude.m4-3975: GCC_TRY_COMPILE_OR_LINK( >> >> configure-79218: case "${target_os}" in >> configure#79219: gnu* | linux* | kfreebsd*-gnu | knetbsd*-gnu | >> solaris*) >> configure-79220: if test x$gcc_no_link = xyes; then >> >> Not sure how to handle such kind of inconsistencies though... > > That's just a bug, there should be no inconsistency.
Yes, of course. Though I'm unaware of any current continous integration setup for gcc, it's about an idea for improvement here - doing something like buildbot-based check here: Have one buildbot instance enabling maintainer-mode using the predefined autotools versions, touch all the .in files, and yell if there is some svn diff after bootstrap. Thanks! /haubi/
