Hello,
On Mon, May 28, 2007 at 10:39:36PM -0700, Paul Eggert wrote:
> [...] Among Autoconf-using programs, I suspect gnulib's stdint
> module makes this macro obsolescent anyway, [...]
I suppose you meant "Automake-using".
Have a nice day,
Stepan Kasal
On Tue, May 29, 2007 at 04:54:52AM +0200, Stepan Kasal wrote:
> I'm going to answer only one of your minor comments now.
Thank you for the explanation of CHECK_FOO vs CHECK_FOOS! The documentation
consistency change seems fine, and my configure.ac snippet becomes
AC_INIT([autotype],[1.0])
AC_CONF
On Tue, May 29, 2007 at 01:31:04PM +0100, Patrick Welche wrote:
> we makes sense thanks to your answer.
^^
which
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
On Tue, May 29, 2007 at 01:31:04PM +0100, Patrick Welche wrote:
> On Tue, May 29, 2007 at 04:54:52AM +0200, Stepan Kasal wrote:
> > I'm going to answer only one of your minor comments now.
>
> Thank you for the explanation of CHECK_FOO vs CHECK_FOOS! The documentation
> consistency change seems fi
Sorry for getting email trigger happy - I seem to still be confused... If
AC_TYPE_UINT8_T
is run on a system without uint8_t, a typdef for uint8_t appears in config.h,
but it is only created at the end of configure, so how would a subsequent
test in configure see the typedef?
Cheers,
Patric
Patrick Welche <[EMAIL PROTECTED]> writes:
> Sorry for getting email trigger happy - I seem to still be confused... If
> AC_TYPE_UINT8_T
> is run on a system without uint8_t, a typdef for uint8_t appears in config.h,
> but it is only created at the end of configure, so how would a subsequent
> t
