regex problems
when trying to upgrade to the latest gnulib regexp, I encountered the following problems: 1. g++ cannot compile regexp: ./regex.h:569: error: expected primary-expression before __restrict__ ./regex.h:569: error: expected `]' before __restrict__ ./regex.h:569: error: expected `,' or `...' before __restrict__ 2. autoconf does not recognize AC_CHECK_HEADERS_ONCE even though I put onceonly.m4 right next to the files that use it in my m4 directory: configure:5675: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:5676: error: possibly undefined macro: AC_CHECK_FUNCS_ONCE thanks. -- Sam Steingold (http://www.podval.org/~sds) running w2k http://www.iris.org.il http://www.camera.org http://www.palestinefacts.org/ http://pmw.org.il/ Bus error -- driver executed. ___ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
Re: [bug-gnulib] regex problems
Sam Steingold wrote: when trying to upgrade to the latest gnulib regexp, I encountered the following problems: 1. g++ cannot compile regexp: ./regex.h:569: error: expected primary-expression before __restrict__ ./regex.h:569: error: expected `]' before __restrict__ ./regex.h:569: error: expected `,' or `...' before __restrict__ This patch should work. No version of g++ in the 3.2.*, 3.3.*, 3.4.*, 4.0.[01] series supports the [__restrict] syntax. *** regex.h 7 Jul 2005 08:08:39 - 1.25 --- regex.h 3 Aug 2005 20:36:47 - *** *** 552,560 # endif # endif #endif ! /* gcc 3.1 and up support the [restrict] syntax. */ #ifndef __restrict_arr ! # if __GNUC__ 3 || (__GNUC__ == 3 __GNUC_MINOR__ = 1) # define __restrict_arr __restrict # else # define __restrict_arr --- 552,560 # endif # endif #endif ! /* gcc 3.1 and up support the [restrict] syntax, but g++ doesn't. */ #ifndef __restrict_arr ! # if (__GNUC__ 3 || (__GNUC__ == 3 __GNUC_MINOR__ = 1)) !defined __cplusplus # define __restrict_arr __restrict # else # define __restrict_arr 2. autoconf does not recognize AC_CHECK_HEADERS_ONCE even though I put onceonly.m4 right next to the files that use it in my m4 directory: configure:5675: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:5676: error: possibly undefined macro: AC_CHECK_FUNCS_ONCE Does the definition of AC_CHECK_HEADERS_ONCE also find its way into the aclocal.m4 file? (Remember that autoconf doesn't look at a directory of m4 files; it looks at an aclocal.m4 file in the current directory.) If yes, the cause is likely to be over-quoting in a .m4 or configure.ac file. Bruno ___ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
Re: [bug-gnulib] regex problems
* Bruno Haible [EMAIL PROTECTED] [2005-08-03 22:42:04 +0200]: Sam Steingold wrote: when trying to upgrade to the latest gnulib regexp, I encountered the following problems: 1. g++ cannot compile regexp: ./regex.h:569: error: expected primary-expression before __restrict__ ./regex.h:569: error: expected `]' before __restrict__ ./regex.h:569: error: expected `,' or `...' before __restrict__ This patch should work. No version of g++ in the 3.2.*, 3.3.*, 3.4.*, 4.0.[01] series supports the [__restrict] syntax. *** regex.h 7 Jul 2005 08:08:39 - 1.25 --- regex.h 3 Aug 2005 20:36:47 - *** *** 552,560 # endif # endif #endif ! /* gcc 3.1 and up support the [restrict] syntax. */ #ifndef __restrict_arr ! # if __GNUC__ 3 || (__GNUC__ == 3 __GNUC_MINOR__ = 1) # define __restrict_arr __restrict # else # define __restrict_arr --- 552,560 # endif # endif #endif ! /* gcc 3.1 and up support the [restrict] syntax, but g++ doesn't. */ #ifndef __restrict_arr ! # if (__GNUC__ 3 || (__GNUC__ == 3 __GNUC_MINOR__ = 1)) !defined __cplusplus # define __restrict_arr __restrict # else # define __restrict_arr will you check this into the gnulib CVS? 2. autoconf does not recognize AC_CHECK_HEADERS_ONCE even though I put onceonly.m4 right next to the files that use it in my m4 directory: configure:5675: error: possibly undefined macro: AC_CHECK_HEADERS_ONCE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:5676: error: possibly undefined macro: AC_CHECK_FUNCS_ONCE Does the definition of AC_CHECK_HEADERS_ONCE also find its way into the aclocal.m4 file? (Remember that autoconf doesn't look at a directory of m4 files; it looks at an aclocal.m4 file in the current directory.) If yes, the cause is likely to be over-quoting in a .m4 or configure.ac file. no, aclocal.m4 does not have the definition. (aclocal is generated by a rule in Makefile.devel: src/autoconf/aclocal.m4 : $(wildcard src/m4/*.m4) $(addsuffix .in,$(CONFIGURES)) egrep '(AC_INIT|AC_PREREQ)' src/configure.in configure.ac cat $(addsuffix .in,$(CONFIGURES)) | egrep -v '(AC_INIT|AC_CONFIG_HEADER|AC_OUTPUT|AC_CONFIG_FILE.*(Makefile|link\.sh)|_CANONICAL_|AC_PREREQ)' configure.ac echo AC_OUTPUT configure.ac aclocal -I `pwd`/src/m4 --output=src/autoconf/aclocal.m4 $(RM) configure.ac ) -- Sam Steingold (http://www.podval.org/~sds) running w2k http://pmw.org.il/ http://www.honestreporting.com http://www.memri.org/ http://www.camera.org http://www.jihadwatch.org/ My other CAR is a CDR. ___ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
