[632] in Zephyr_Bugs
Re: regcomp problems in solaris 2 (zephyr 2.0 beta 2) with fix
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Jul 13 01:54:31 1995
Date: Thu, 13 Jul 1995 01:56:02 -0400
From: Greg Hudson <ghudson@MIT.EDU>
To: "E. Jay Berkenbilt" <ejb@ERA.COM>
Cc: bug-zephyr@MIT.EDU
In-Reply-To: "[620] in Zephyr_Bugs"
> BTW, in order to run autoheader, I had to pull h/zephyr/zephyr.h out
> of AC_CONFIG_HEADER and stick it in AC_OUTPUT instead. There is
> nothing in h/zephyr/zephyr.h.in requires it to be in
> AC_CONFIG_HEADER anyway, and an h/zephyr/zephyr.h that was older
> than zephyr.h.in was included in the distribution. Was
> h/zephyr/zehpyr.h listed under AC_CONFIG_HEADER because of
> oversight, or is there a reason it should be there? In any case,
> that change is also included in this patch. (For the moment, I am
> also running autoconf 2.3, but I will probably install 2.4 soon.)
As zephyr.h is a header file, it should be processed using the header
file mechanism, not the less convenient Makefile substitution
mechanism. The NOTES file in the source tree explains the autoheader
bug, and how to work around it:
If you want to run "autoheader" to regenerate h/config.h.in in
the source tree, you should know that autoconf 2.3's
autoheader has a bug which prevents it from finding the right
header file to use when multiple output header files are
specified. I've sent in a patch for this, but until the next
release, use:
autoheader configure.in > h/config.h.in
I checked the 2.0 beta 2 release directory, and there is no
h/zephyr/zephyr.h included in it.
I turned your AC_TRY_RUN test for regcomp into a macro (putting it in
aclocal.m4) and sent off a version of it to bug-gnu-utils for possible
inclusion into Autoconf. So the final 2.0 release should fix your
regcomp problem.
