Eric Blake wrote:
> Can/should we work around this gcc bug, by ensuring that is
> always included prior to in all configure tests?
I think it goes too far to attempt to work around bugs of every possible
gcc version on every possible platform.
- The number of users of that particular version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 9/19/2009 7:16 AM:
> I agree with you that it was a problem with that particular gcc, because
> - the build works fine with the CC="cc -Ae -D_XOPEN_SOURCE=500" setting
> mentioned in the INSTALL file,
> - as you fou
Greg Wooledge wrote:
> The gcc bootstrap finally finished. The failure I reported does not
> occur with gcc 3.4.6 (+ GNU as) built from source on the same target
> machine. Whether this indicates a problem with the binary gcc build I
> was using (specifically, its generated header files), or a pr
The gcc bootstrap finally finished. The failure I reported does not
occur with gcc 3.4.6 (+ GNU as) built from source on the same target
machine. Whether this indicates a problem with the binary gcc build I
was using (specifically, its generated header files), or a problem in
m4's ./configure, I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding gnulib]
According to Greg Wooledge on 9/18/2009 9:52 AM:
> GNU m4 1.4.13 fails to build on HP-UX 11.11:
>
> make[4]: Entering directory `/usr/local/src/m4-1.4.13/lib'
> CC gl_avltree_oset.o
> In file included from sys/wait.h:91,
>
