Re: Error because README is missing
%% Akim Demaille [EMAIL PROTECTED] writes: ad Finally, note that you are allowed to ask config.status to perform ad substitutions on files it doesn't know[1]. In your case, I'm unsure ad binding the instantiation to configure instead of make is right. Doh! I thought this would be the perfect answer but I completely forgot: the whole point behind build.sh is that you _DON'T HAVE A MAKE PROGRAM_! This shell script lets you build the GNU make distribution on a system with no native make installed. So, I can't put the rules to build the build.sh file in the Makefile, since when you need build.sh there will not be any make to run the Makefile. I suppose I could tell those folks to run the config.status step by hand, but I'd really like to get this built through the configure script. Ideas? -- --- Paul D. Smith [EMAIL PROTECTED] HASMAT--HA Software Mthds Tools Please remain calm...I may be mad, but I am a professional. --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them.
Re: Relative path in CPPFLAGS and distcheck
Alexandre Duret-Lutz wrote:
[Please reply to [EMAIL PROTECTED]
Robert == Robert Lowe [EMAIL PROTECTED] writes:
Robert Hi!
Robert I have a set of common headers files in includes/ and the following
Robert line in configure.ac:
Robert AC_SUBST(CPPFLAGS,[-I../includes])
Should be
AC_SUBST([AM_CPPFLAGS], ['-I$(top_srcdir)/includes'])
or
AC_SUBST([AM_CPPFLAGS], ['-I$(top_srcdir)/includes -I$(top_builddir)/includes'])
if you have built headers.
See the thread RFC for new FAQ entry: Flag Variables Ordering
on the Automake lists to understand why redefining plain
CPPFLAGS is wrong.
Thank you for the pointers!
Robert ...since all source files are in parallel directories.
(The above doesn't require this.)
Well, make distcheck is still failing, but not on every box I've
tried it. I thought I would distill everything down to a simple
'hello, world' example (with a built header and a copy of stdio.h)
which you can find at:
http://www.lawrence.edu/fast/lower/hello-0.5.tar.gz
(it has to replicate there, but should be there by 20:30 GMT)
From that, configure.ac is:
# -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.
AC_INIT(hello,0.5)
AM_INIT_AUTOMAKE(hello,0.5)
AC_CANONICAL_HOST
# Checks for programs.
AC_PROG_CC
AC_PROG_INSTALL
AC_CREATE_STDINT_H([${srcdir}/includes/_stdint.h])
AC_SUBST(AM_CPPFLAGS,['-I$(top_srcdir)/includes
-I$(top_builddir)/includes'])
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_FILES([Makefile src/Makefile])
AC_OUTPUT
...and, Makefile.am:
SUBDIRS = src
EXTRA_DIST = reconf
noinst_HEADERS = includes/stdio.h
...and, src/Makefile.am:
bin_PROGRAMS = hello
hello_SOURCES = hello.c
hello_CFLAGS = -Wall -pedantic
A make distcheck with this example fails on my home system with FC3
running on an AMD Athlon, but *succeeds* on an Intel box running an
older Linux kernel, and older versions of autoconf/automake. I know
that's a lot of variables. Perhaps I've still not learned something
I should have, or am I running into some other problem?
*FAILS*:
Linux 2.6.9-1.667 #1 Tue Nov 2 14:50:10 EST 2004 x86_64 x86_64 x86_64
GNU/Linux
$ autoconf --version
autoconf (GNU Autoconf) 2.59
...
$ automake --version
automake (GNU automake) 1.9.3
...
*SUCCEEDS*:
Linux 2.4.21-9.ELsmp #1 SMP Thu Jan 8 17:08:56 EST 2004 i686 i686 i386
GNU/Linux
# autoconf --version
autoconf (GNU Autoconf) 2.57
...
# automake --version
automake (GNU automake) 1.6.3
...
[...]
Robert Also, is it perfectly legit to list these files in the top-level
Robert Makefile.am as EXTRA_DIST, rather than explicitly listing this
Robert subdirectory, adding a Makefile.am there, ... since there's
Robert nothing to build there?
Yes. However you'd better use noinst_HEADERS instead of
EXTRA_DIST so that `make tags' and friends process the headers.
Again, thank you for the correction!
-Robert
Re: Error because README is missing
* Paul Smith wrote on Sun, Dec 05, 2004 at 08:25:56PM CET: %% Akim Demaille [EMAIL PROTECTED] writes: ad Finally, note that you are allowed to ask config.status to perform ad substitutions on files it doesn't know[1]. In your case, I'm unsure ad binding the instantiation to configure instead of make is right. Doh! I thought this would be the perfect answer but I completely forgot: the whole point behind build.sh is that you _DON'T HAVE A MAKE PROGRAM_! This shell script lets you build the GNU make distribution on a system with no native make installed. So, I can't put the rules to build the build.sh file in the Makefile, since when you need build.sh there will not be any make to run the Makefile. I suppose I could tell those folks to run the config.status step by hand, but I'd really like to get this built through the configure script. Ideas? dnl ... AC_CONFIG_FILES([Makefile]) AC_OUTPUT touch foo.in ./config.status --file foo What am I missing? Regards, Ralf
Re: Error because README is missing
* Stepan Kasal wrote on Mon, Dec 06, 2004 at 10:03:27AM CET: Hello, On Mon, Dec 06, 2004 at 09:28:17AM +0100, Ralf Wildenhues wrote: AC_OUTPUT touch foo.in ./config.status --file foo why the ``touch''? (./config.status doesn't check the timestamps.) Oh, that was just copy-n-paste from the example I tested, the `touch' creates the file. :-) But while we're at it, since Automake uses $SHELL with config.status, maybe it's more portable to do it as well (I don't know): $SHELL ./config.status --file foo Regards, Ralf
Re: Error because README is missing
%% Ralf Wildenhues [EMAIL PROTECTED] writes: I suppose I could tell those folks to run the config.status step by hand, but I'd really like to get this built through the configure script. Ideas? rw dnl ... rw AC_CONFIG_FILES([Makefile]) rw AC_OUTPUT rw touch foo.in rw ./config.status --file foo rw What am I missing? I wasn't sure config.status would be available while (my part of) configure was still running. I guess if all AC_OUTPUT does is run config.status --file then that would make sense, but it could also do the translation inline. I'll give it a try; cheers! -- --- Paul D. Smith [EMAIL PROTECTED] HASMAT--HA Software Mthds Tools Please remain calm...I may be mad, but I am a professional. --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them.
Re: CXXLINK in generated Makefiles
On Sun, Dec 05, 2004 at 06:55:23AM +0100, Alexandre Duret-Lutz wrote: Dale AC_SUBST(CXX) This is superfluous if you already call AC_PROG_CXX. OK, I've wondered about that. Dale AC_SUBST(CXXLINK) This will override the Automake definition of this variable with the configure definition of it (which is empty, unless you set the variable explicitly). I see. Dale Any package including C++ code must define the output variable `CXX' in Dale `configure.ac'; the simplest way to do this is to use the `AC_PROG_CXX' Dale macro (*note Particular Program Checks: (autoconf)Particular Programs.). This means that CXX is not defined by Automake. OK, after digesting this email thread I can see how it could mean that. Dale A few additional variables are defined when a C++ source file is Dale seen: Dale [snip] Dale `CXXLINK' Dale The command used to actually link a C++ program. This means that CXXLINK is defined by Automake in Makefiles with C++ source files. It does not means that CXXLINK is defined at configure time. Automake just defines the variable in the Makefile.ins it outputs. Perhaps that part of the documentation could be more explicit. Automake does not define CXX - that must be defined externally. To have autoconf define it, many applications use AC_PROG_CXX. The following are defined by automake in generated Makefiles or something like that. I can't think of any clean way to obtain the Automake definition of CXXLINK for a non-Automake Makefile. (One idea would be to generate your Makefile.common.in by extracting the interesting bits of an automake-generated Makefile.in.) I'll mull that one over. I believe the simplest solution is to call libtool as you always did, and simply add the missing --tag=CXX option. The problem with that is that libtool 1.5 does not support that option and dies an ugly death when it's present. I guess I need to figure out how to write an autoconf test to figure out the libtool version. Any suggestions welcome - I'm certainly no autoconf wizard! Thanks, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available
29, 900 English pages for Libtool library used but LIBTOOL is undefined
Maybe someone can figure out a better error message, please? For those that found *this* message because of the subject line: http://lists.gnu.org/archive/html/bug-automake/2004-07/msg00083.html Stephan although AC_PROG_LIBTOOL _is_ present in configure.ac. Therefore it means AC_PROG_LIBTOOL is not evaluated. This is certainly because AC_PROG_LIBTOOL is not defined in aclocal.m4. This is probably because aclocal does not see libtool.m4 in its search path. This is might be because Automake and Libtool are installed with different --prefix; for instance Libtool in /usr and Automake in /usr/local. ... See the Automake manual's Macro search path section for more discussion about dirlist.
Libtool library used but LIBTOOL is undefined
Hi, On Mon, Dec 06, 2004 at 12:57:50PM -0800, Bruce Korb wrote: Subject: 29, 900 English pages for Libtool library used but LIBTOOL is undefined google is exaggerating, of course. When you enter Libtool library used but LIBTOOL is undefined with the quotes, you only get 76 different pages in all languages. Have a nice day, Stepan Kasal
Re: Libtool library used but LIBTOOL is undefined
On Monday 06 December 2004 01:18 pm, Stepan Kasal wrote: Hi, On Mon, Dec 06, 2004 at 12:57:50PM -0800, Bruce Korb wrote: Subject: 29, 900 English pages for Libtool library used but LIBTOOL is undefined google is exaggerating, of course. Of course it is. That doesn't mean that the error message is informative, though. :)
