www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Lancaster <...@grubby.net>
Subject config/8323: buildconf bugs out with undefined macros AC_LANG*
Date Wed, 12 Sep 2001 07:48:36 GMT

>Number:         8323
>Category:       config
>Synopsis:       buildconf bugs out with undefined macros AC_LANG*
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Sep 12 00:50:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     tom@grubby.net
>Release:        v2.0.26-de
>Organization:
apache
>Environment:
Linux mifune 2.4.3 #5 Thu May 31 17:53:38 PDT 2001 i686 unknown
gcc version 2.95.4 20010810 (Debian prerelease)

>Description:
mifune:/home/tom/experimental/httpd-2.0# ./buildconf               
rebuilding srclib/apr/configure
buildconf: checking installation...
buildconf: autoconf version 2.13 (ok)
buildconf: libtool version 1.4b

1996, (ok)
Copying libtool helper files ...
Creating include/arch/unix/apr_private.h.in ...
Creating configure ...
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_LANG_PUSH
***BUG in Autoconf--please report*** AC_LANG_POP
***BUG in Autoconf--please report*** AC_LANG_PUSH
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_MSG_NOTICE
***BUG in Autoconf--please report*** AC_LANG_POP
***BUG in Autoconf--please report*** AC_LANG_PUSH
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_POP
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
rebuilding srclib/apr-util/configure
Creating include/private/apu_config.h ...
Creating configure ...
Invoking xml/expat/buildconf.sh ...
Incorporating /usr/share/aclocal/libtool.m4 into aclocal.m4 ...
Copying libtool helper files ...
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `conftools'.
Creating config.h.in ...
Creating configure ...
configure.in:75: AC_PROG_CPP was called before AC_PROG_CC
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_LANG_PUSH
***BUG in Autoconf--please report*** AC_LANG_POP
***BUG in Autoconf--please report*** AC_LANG_PUSH
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_MSG_NOTICE
***BUG in Autoconf--please report*** AC_LANG_POP
***BUG in Autoconf--please report*** AC_LANG_PUSH
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_POP
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
***BUG in Autoconf--please report*** AC_LANG_PROGRAM
rebuilding srclib/pcre/configure
rebuilding include/ap_config_auto.h.in
rebuilding configure


>How-To-Repeat:
Following the instructions from the mod_perl-2.0 pod docs, as follows:
 % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co httpd-2.0
        % cd httpd-2.0/srclib
        % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co apr
        % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co apr-util
        % cd ..
        % ./buildconf
       
... Things stopped as noted above at the buildconf stage - not sure if this is a problem with
the apr and apr-util parts.
>Fix:
I'm afraid I can't suggest any way to fix this. My stone-age attempt consisted of commenting
out the offending lines inthe configure file. This did not work.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 


Mime
View raw message