or term.h... yes
Thanks for the bug report. Please read
<http://www.gnu.org/software/autoconf/manual/html_node/Present-But-Cannot-Be-Compiled.html>
and then show that to the maintainer of the package you're building, who
can fix this in his package. The error becomes clearer if you l
checking term.h usability... no
checking term.h presence... yes
configure: WARNING: term.h: present but cannot be
compiled
configure: WARNING: term.h: check for missing
prerequisite headers?
configure: WARNING: term.h: proceeding with the
preprocessor's result
configure: WARNING: ##
---
Look at the line(s) concerning Emacs. There isn't any path information.
m4 was upgraded to m4-1.4.8 before autoconf-2.60 attempted installation
make was upgraded to make-3.81 before autoconf-2.60 attempted
installation
## - ##
## GNU Autoconf 2.60 test suite. ##
## ---
Hello Tony,
* Tony Jennings - Jensoft Ltd wrote on Thu, Sep 14, 2006 at 12:40:08AM CEST:
> The attached log shows a bug reported during running configure in
> coreutils-5.0
Thanks for the bug report.
> moonraker> cd coreutils-5.0
> moonraker> ./configure
> checking build
The attached log shows a bug reported during running configure in coreutils-5.0
The output asks to have this reported to gnu.org
Kind regards,
Tony Jennings
Jensoft Ltd
0870 285 6038
moonraker> tar xf coreutils-5.0.tar
moonraker> cd coreutils-5.0
moonraker> ./configure
checking build system type
Hi,
I got the following message running a configure script on my Powerbook
G4 under
Mac OS X v10.3 - don't know if this is relevant, but ...
Cheers,
Martin
checking resolv.h presence... yes
configure: WARNING: resolv.h: present but cannot be compiled
configure: WARNING: resolv.h: check for missin
Kelley Cook wrote:
If you run autoheader 2.59b on a configure.ac without a
AC_CONFIG_HEADERS, it will properly inform you
error: AC_CONFIG_HEADERS not found in configure.ac
Nevertheless the perl script continues which appends .in to nothing
thereby creating the hidden file ".in" and procedes all
Kelley Cook <[EMAIL PROTECTED]> writes:
> 2004-12-12 Kelley Cook <[EMAIL PROTECTED]>
>
> * bin/autoheader.in: Exit if no AC_CONFIG_HEADERS was found.
Thanks; I installed that.
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/ma
If you run autoheader 2.59b on a configure.ac without a
AC_CONFIG_HEADERS, it will properly inform you
error: AC_CONFIG_HEADERS not found in configure.ac
Nevertheless the perl script continues which appends .in to nothing
thereby creating the hidden file ".in" and procedes all outputs all the
d
$>./configure
func_success failed.
func_success failed.
No shell found that supports shell functions.
Please tell [EMAIL PROTECTED] about your system,
including any error possibly output before this
message
checking for a BSD-compatible install... /usr/bin/install -c
... (then works normally)
Syst
trying to configureon a sun ultra2 running solaris 8 with dual 400mhz ultra
sparc II's and 1280 mb ram.
configure: WARNING: netinet/ip.h: present but cannot be compiled
configure: WARNING: netinet/ip.h: check for missing prerequisite headers?
configure: WARNING: netinet/ip.h: proceeding with the p
See below.
Original Message
Subject: bug report
From:"Martin Herrman" <[EMAIL PROTECTED]>
Date:Tue, June 24, 2003 8:18 pm
To: [EMAIL PR
Chris Schuit @ Euronet writes:
> configure: WARNING: net/if.h: present but cannot be compiled
> configure: WARNING: net/if.h: check for missing prerequisite headers?
> configure: WARNING: net/if.h: proceeding with the preprocessor's result
> configure: WARNING: ## --
configure: WARNING: net/if.h: present but cannot be compiled
configure: WARNING: net/if.h: check for missing prerequisite headers?
configure: WARNING: net/if.h: proceeding with the preprocessor's result
configure: WARNING: ## ##
configure: WARNING: ## Re
|Hi. I'm the maintainer of the Debian package for Autoconf. I
|received the following bug report against Autoconf 2.52. It
|looks like it still applies to Autoconf 2.53, so I'm passing it
|along upstream with this message.
|
|Thanks,
|
|Ben.
|
|From: & Youngman <[EMAIL PRO
Hi. I'm the maintainer of the Debian package for Autoconf. I
received the following bug report against Autoconf 2.52. It
looks like it still applies to Autoconf 2.53, so I'm passing it
along upstream with this message.
Thanks,
Ben.
Start of forward
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> To be strict, the testsuite doesn't guarantee it because macros
Pavel> can expand differently dependent e.g. on the number of
Pavel> arguments.
I agree.
Pavel> Anyway, I agree with your decision.
I agree too :)
Pavel> I can, b
Hello, Akim!
> | > autoconf: Undefined macros:
> | > ***BUG in Autoconf--please report*** AC_FD_CC
> | > ***BUG in Autoconf--please report*** AC_FD_CC
> | > ***BUG in Autoconf--please report*** AC_FD_CC
> | > configure.in:2:AC_CHECK_TOTO
> |
> | That's not really helpful, I know.
>
>
| > autoconf: Undefined macros:
| > ***BUG in Autoconf--please report*** AC_FD_CC
| > ***BUG in Autoconf--please report*** AC_FD_CC
| > ***BUG in Autoconf--please report*** AC_FD_CC
| > configure.in:2:AC_CHECK_TOTO
|
| That's not really helpful, I know.
And in fact most of
Emmanuel Beffara writes:
> AC_DEFINE(AC_CHECK_TOTO,
> AC_TRY_COMPILE([#include ], [toto()],
> TOTO=true, TOTO=false))
AC_DEFUN
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Hello, Emmanuel!
> AC_DEFINE(AC_CHECK_TOTO,
> AC_TRY_COMPILE([#include ], [toto()],
> TOTO=true, TOTO=false))
You should always quote the arguments, especially when you expect
expansion of the arguments, otherwise it happens in a wrong order!
> autoconf: Undefined
On Oct 5, 2000, Emmanuel Beffara <[EMAIL PROTECTED]> wrote:
> AC_DEFINE(AC_CHECK_TOTO,
> AC_TRY_COMPILE([#include ], [toto()],
> TOTO=true, TOTO=false))
You're missing quoting. Enclose macro arguments in `[]'s.
AC_DEFINE(AC_CHECK_TOTO,
[AC_TRY_COMPILE(
Hello.
This is a report for a bug I confess I don't understand well...
The bug started when I added an `acinclude.m4' to my configuration
script. In fact it comes from a mistake: I wrote "AC_DEFINE" instead
of "AC_DEFUN" in the auxiliary macro file. Here is a minimized version
of the bug:
confi
Hi!
The current CVS version of Autoconf no longer defines AC_LOCALDIR
which you appear to be depending on in your configure.in script.
Would it be possible to see how and why you use it so that either I
may submit a patch to you, or to Autoconf? A pointer to a tarball is
just what is needed.
T
>
> | gnu m4 1.4
> | autoconf 2.13
> | AIX 4.3.2
> |
> | # autoconf
> | autoconf: Undefined macros:
> | ***BUG in Autoconf--please report*** AC_LOCALDIR
>
> Arg, this is a known difference between CVS autoconf and 2.13: in the
> latter there is:
>
> if test -n "$localdir"; then
> use_localdi
> "Assar" == Assar Westerlund <[EMAIL PROTECTED]> writes:
Assar> Now, this `feature' is gone from the CVS version of autoconf so
Assar> that code should probably migrate to doing things some other
Assar> way, but that's probably somebody else's problem.
Right. Where can we see that package?
| gnu m4 1.4
| autoconf 2.13
| AIX 4.3.2
|
| # autoconf
| autoconf: Undefined macros:
| ***BUG in Autoconf--please report*** AC_LOCALDIR
Arg, this is a known difference between CVS autoconf and 2.13: in the
latter there is:
if test -n "$localdir"; then
use_localdir="-I$localdir -DAC_LOCALDIR
Jeffrey Altman <[EMAIL PROTECTED]> writes:
> When I run autoconf I get the error I sent you.
>
> grep'ing the files the error is occuring because the AC_LOCALDIR which
> is in the aclocal.m4 file is not defined to a value.
>
> I will check with MIT to make sure that what I was told was accurate.
All I am attempting to do is convert the configure.in files that come
with the Kerberos distribution into a ./configure which I can run.
I was told by MIT to retrieve the latest m4 and autoconf from
ftp.gnu.org. So that is what I did.
When I run autoconf I get the error I sent you.
grep'ing the
> Jeffrey Altman <[EMAIL PROTECTED]> writes:
> > gnu m4 1.4
> > autoconf 2.13
> > AIX 4.3.2
> >
> > # autoconf
> > autoconf: Undefined macros:
> > ***BUG in Autoconf--please report*** AC_LOCALDIR
>
> Can you send a minimal configure.in that gives this error? Thanks.
>
> /assar
>
The Kerberos
Jeffrey Altman <[EMAIL PROTECTED]> writes:
> The Kerberos V5 distribution contains an aclocal.m4 file with the
> following reference:
>
> AC_PREREQ(2.12)
> dnl
> dnl Figure out the top of the source and build trees. We depend on
> localdir
> dnl being a relative pathname; we could make it genera
Jeffrey Altman <[EMAIL PROTECTED]> writes:
> gnu m4 1.4
> autoconf 2.13
> AIX 4.3.2
>
> # autoconf
> autoconf: Undefined macros:
> ***BUG in Autoconf--please report*** AC_LOCALDIR
Can you send a minimal configure.in that gives this error? Thanks.
/assar
gnu m4 1.4
autoconf 2.13
AIX 4.3.2
# autoconf
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_LOCALDIR
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * N
Thanks for the report. Since then Autoconf uses Automake, so such
failures are less likely. Nonetheless, I don't understand why frozen
files should be taken from srcdir.
Akim
The "Makefile.in" file distributed with autoconf appears to be incorrect.
There are two problems, one of which I've hit and the other of which I
don't intend to try:
The "install" target, when it installs the scripts, does not install them
from the source directory. Thus, if you are using GNU
35 matches
Mail list logo
