GNU bug report logs - #30352
BUG report using autoconf…

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 30352 in the body.
You can then email your comments to 30352 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: aotto <aotto1968 <at> t-online.de>
To: bug-automake <at> gnu.org
Subject: BUG report using autoconf…
Date: Sun, 4 Feb 2018 23:30:01 +0100

Hi,

the following line create a BUG in autoconf
> # if 'CFLAGS' is NOT set, than macro 'AC_PROG_CC' set 'CFLAGS=-g -O2'
in seems that a M4-MACRO in COMMENT is a problem.

without this line… it works.

#       then increment AGE.
#
#    6. If any interfaces have been removed since the last public release,
#       then set AGE to 0.
#
#     *_Never_* try to set the interface numbers so that they correspond
#  to the release number of your package.  This is an abuse that only
#  fosters misunderstanding of the purpose of library versions. Instead,
#  use the `-release' flag (*note Release numbers::), but be warned that
#  every release of your package will not be binary compatible with any
#  other release.
AC_SUBST([VERSION_INFO], [22:0:0])

AC_CONFIG_MACRO_DIR([m4])

# if 'CFLAGS' is NOT set, than macro 'AC_PROG_CC' set 'CFLAGS=-g -O2'
CFLAGS="-Wall -Wcast-align"
CXXFLAGS=""

AC_PROG_CC
AM_PROG_AR
AC_PROG_CXX
AC_PROG_CC_C99
if test "$ac_cv_prog_cc_c99" = "no"; then AC_MSG_ERROR([require c99 mode 
to compile]); fi

if test "$build_os" != "cygwin"; then CFLAGS="-fvisibility=hidden 
$CFLAGS"; fi
SC_ENABLE_THREADS

#------------------------------------
AC_MSG_CHECKING(get libtool support);echo
#------------------------------------
AC_DISABLE_STATIC
LT_INIT
LT_LIB_DLLOAD

#------------------------------------
AC_MSG_CHECKING(programs);echo
#------------------------------------
"configure.ac" 267L, 9761C geschrieben

#> autoconf
configure.ac:79: error: possibly undefined macro: AC_PROG_CC
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

#> autoconf
#> autoconf

# autoconf -V
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, 
<http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.


mfg ao

Message #8 received at 30352 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Lirzin <mthl <at> gnu.org>
To: aotto <aotto1968 <at> t-online.de>
Cc: 30352 <at> debbugs.gnu.org
Subject: Re: bug#30352: BUG report using autoconf…
Date: Sun, 04 Feb 2018 23:56:33 +0100

Hello,

aotto <aotto1968 <at> t-online.de> writes:

> the following line create a BUG in autoconf
>> # if 'CFLAGS' is NOT set, than macro 'AC_PROG_CC' set 'CFLAGS=-g -O2'
> in seems that a M4-MACRO in COMMENT is a problem.

Since the issue is related to Autoconf please report it to
<bug-autoconf <at> gnu.org> instead.

Thanks.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.