[prev in list] [next in list] [prev in thread] [next in thread] 

List:       autoconf-bug
Subject:    Re: Autoconf requires m4 and m4 requires autoconf
From:       Eric Blake <ebb9 () byu ! net>
Date:       2010-01-03 15:14:17
Message-ID: 4B40B449.8060500 () byu ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Chris Karakas on 1/3/2010 8:04 AM:
> test-ftello.c:119: assertion failed
> ./test-ftello.sh: line 3: 11120 Aborted                 ./test-ftello${EXEEXT} 1 \
>                 <"$srcdir/test-ftello.sh"
> FAIL: test-ftello.sh

> But now, what do I do with the failed test? Do I really have to report to \
> bug-m4@gnu.org, or can we continue from here?

That is a known bug in your ancient glibc (and one that is frequently
reported to both bug-m4 and bug-gnulib, since m4 is borrowing that code
from gnulib).  Basically, your glibc is so old that it has a broken
ungetc(), and no one has bothered to write a gnulib workaround patch for
it (it's easier to upgrade to a newer glibc, where the bug has been fixed,
than it is to figure out a workaround).  M4 does not tickle that
particular ungetc bug, so m4 is immune; but the failure does point out
that unless you upgrade your glibc, you may have other programs on your
system that fail to comply to POSIX depending on how they use ungetc().
(And if you do report it to bug-m4, you'll get the same answer, since I'm
the maintainer of both autoconf and m4 ;)

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktAtEkACgkQ84KuGfSFAYChGwCffpoMpQVjjon0D7RfkzB63WJb
hBgAn19lU7dBfEAPS4LP6D76+wJwt9Q8
=1bSY
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread]