[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE
From: |
Stepan Kasal |
Subject: |
Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE |
Date: |
Wed, 10 Aug 2005 11:06:12 +0200 |
User-agent: |
Mutt/1.4.1i |
Hello,
On Sun, Aug 07, 2005 at 01:21:04PM -0400, Sam Steingold wrote:
> > Maybe this trick is not working reliably; aclocal was not designed for
> > this... Could you post the ad hoc created configure.in?
so it seems the problem is in regex.m4, which comes from gnulib.
Thus I cc this post to bug-gnulib.
The macro gl_INCLUDED_REGEX contains this:
m4_syscmd([test -f '$1'])
ifelse(m4_sysval, 0,
[ ...
gl_PREREQ_REGEX
])
Macro gl_PREREQ_REGEX, which calls AC_CHECK_HEADERS_ONCE, is
expanded only if the current directory contains the file "regex.c"
(the argument to gl_INCLUDED_REGEX).
For Sam: so the magic workaround should be to touch the file "regex.c"
in the same directory where you have your artificial configure.in.
For gnulib people:
Why is the above trick necessary? Why should the macro expansion
depend on the presence of the file?
Second: just above the quoted code:
test -n "$1" || AC_MSG_ERROR([missing argument])
yes, the macro gl_INCLUDED_REGEX requires a parameter, but why it should
be reported in runtime? (Yes, the parameter might be a shell variable,
but is this done often?)
Third, the name regex.m4 conflicts with a file in Automake. This can
cause problems with "aclocal --include". Could we perhaps rename it?
Fourth, I noticed a typo; could you please apply the attached patch?
Fifth: when my "minmax" patch is resolved (Bruno ;-), shouldn't
something similar go to onceonly*.m4, too?
Have a nice day,
Stepan Kasal
gnulib-20050810-once257.patch
Description: Text document
- error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Sam Steingold, 2005/08/05
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/06
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Sam Steingold, 2005/08/06
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/07
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Sam Steingold, 2005/08/07
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE,
Stepan Kasal <=
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Bruno Haible, 2005/08/10
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Paul Eggert, 2005/08/23
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Sam Steingold, 2005/08/23
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/24
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Sam Steingold, 2005/08/24
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/25
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/25
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Sam Steingold, 2005/08/25
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/25
- Message not available
- Re: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE, Stepan Kasal, 2005/08/25