Re: Makefile.in and Makefile not generated when using a static library

/Random/Makefile Makefile ]) AC_OUTPUT Also, instead of running aclocal, libtoolize, autoconf, and automake by hand, just run autoreconf -i -- William Pursell

Re: Makefile.in and Makefile not generated when using a static library

and in building static libraries with automake, so correct me if I'm wrong!). Is there any reason to avoid LT_INIT and use AC_PROG_RANLIB instead? I thought that AC_PROG_RANLIB was considered deprecated, so that LT_INIT would be preferred here. -- William Pursell

Re: silent installs

curtains. Probably no curtains, but they do have windshield wiper to clear away the cruft. -- William Pursell

Re: how to install library in a specific directory?

maintainer should not be deciding where the user must install the library. If the user wants to install ezproject in /opt/ezproject, he should to be able to do 'configure --libdir=/opt/ezproject/lib', but your setup will not allow that. -- William Pursell

documentation grammaro

diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 4b08042..455d1c4 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -8109,7 +8109,7 @@ functional might let your @command{configure} accept a header which causes some @emph{compiler} error. Do not hesitate to check a header with

Re: RFE: allow for computed version number

to clone the git repository? -- William Pursell

Re: running tests under in a tests/ directory

and install your own code on the box, then you can install automake as well. (Where 'install' might mean 'put in $HOME') -- William Pursell

Re: binary distribution build with automake

, but there are a few cases where I need to have the generated snippet file be just the rule, so I can do things like: check-local: @MY_LOCAL_RULES@ The question is: is that a reliable technique, or is it a ridiculous hack that will someday come to haunt me? -- William Pursell

summarize misbehaving tests

environment option, an automake option (like color-tests), or just leave it in for all invocations of make check? (or do you think it's a bad idea?) -- William Pursell

Re: summarize misbehaving tests

Ralf Wildenhues wrote: Hi William, * William Pursell wrote on Fri, Jan 30, 2009 at 08:02:58AM CET: I've written a simple patch that lists the tests that misbehaved (failed or unexpectedly passed), one per line, in the banner. Do you think it would be appropriate to make

Re: automake less verbose (iter 3.1)

Jan Engelhardt wrote: On Monday 2008-12-15 08:32, William Pursell wrote: Jan Engelhardt wrote: third round here of the automake-tranquility patch from me. Updates from previous attempts: I've been looking through the archive and haven't noticed any followup on this. I don't know

[PATCH] Fix treatment of --enable-assert in AC_HEADER_ASSERT

diff --git a/ChangeLog b/ChangeLog index a250ee2..bde246f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2008-12-06 William Pursell [EMAIL PROTECTED] + + Fix AC_HEADER_ASSERT to honor --enable-assert, rather than + treat --enable-assert and --disable-assert equivalently

Re: [PATCH] Fix treatment of --enable-assert in AC_HEADER_ASSERT

William Pursell wrote: a patch that has nothing to do with automake Oops. That went to the wrong list. Please disregard. -- William Pursell

Re: [PATCH 1/3] Replace 'automake' with @command{automake} where appropriate in automake.texi

Ralf Wildenhues wrote: * William Pursell wrote on Mon, Dec 01, 2008 at 10:06:10PM CET: @@ -11677,7 +11677,7 @@ A major and long-awaited release, that comes more than two years after @item The new dependency tracking scheme that uses @command{depcomp}. Aside from the improvement

Re: [PATCH 1/3] Replace 'automake' with @command{automake} where appropriate in automake.texi

Ralf Wildenhues wrote: * William Pursell wrote on Mon, Dec 01, 2008 at 10:06:10PM CET: @@ -11677,7 +11677,7 @@ A major and long-awaited release, that comes more than two years after @item The new dependency tracking scheme that uses @command{depcomp}. Aside from the improvement

CVS in documentation

I've been thinking about re-writing the section in the manual that discusses keeping derived files in CVS to make it tool neutral. There are some details about timestamps that are pretty CVS specific, and it seems out of place (and obsolete). Any thoughts? -- William Pursell

[PATCH 3/3] Simple typographical and grammar errors in automake.texi.

-- 1.6.0.4.782.geea74.dirty -- William Pursell

[PATCH 2/3] Replace 'configure' with '@command{configure}' as appropriate.

-- 1.6.0.4.782.geea74.dirty -- William Pursell

[PATCH 1/3] Replace 'automake' with @command{automake} where appropriate in automake.texi

of compilation, there is a bootstrapping problem when header files are generated by running a program. The problem is that, the first time the build is done, there is no way by default to know that the headers are -- 1.6.0.4.782.geea74.dirty -- William Pursell

Re: maude_ vs LIBRARY_

Ralf Wildenhues wrote: * William Pursell wrote on Sun, Nov 23, 2008 at 10:05:06AM CET: I suggest changing, eg, LIBRARY_LIBTOOLFLAGS to libmaude_LIBTOOLFLAGS. Unless we can come up with a definite improvement in consistency, I wouldn't want to change things. What about changing

[PATCH] documentation errors

have succesfully used program_CFLAGS and have never used AM_PROG_CC_C_O, so I believe this is out of date. commit 3a31de76f19c0db0645faaa2388b26bf85c5989d Author: William Pursell [EMAIL PROTECTED] Date: Sun Nov 23 17:01:22 2008 + Typos thru 8.7 diff --git a/ChangeLog b/ChangeLog index

[PATCH 1/3] quotes in configure.ac

AC_REQUIRE_AUX_FILE. I found the sentence somewhat oddly constructed on first reading, but in retrospect I now like the original wording best. commit 1b8fb7d8cbfeedc7f6c41ac2ce30d561cf8acd0c Author: William Pursell [EMAIL PROTECTED] Date: Sat Nov 22 12:17:58 2008 + Quote APIVERSION

[PATCH 3/3] automake.texi/ChangeLog

commit 7662273966ac796795cfd8fec06a9d8e610767ac Author: William Pursell [EMAIL PROTECTED] Date: Sat Nov 22 12:40:21 2008 + Typos, grammar, and minor changes to texinfo. Fixed url of config on savannah. (s/cvs/git/) Remove punctuation from top level Include menu item

Re: [PATCH 1/3] quotes in configure.ac

having no arguments, or an empty argument, but I don't see any value in allowing users to use that. What would be the gain? That's my mistake I've gotten overly zealous about quoting in m4 macros and mistook the brackets, not realizing they were indicating optional arguments. -- William Pursell

[PATCH] typo in automake.texi

an Automake rule or definition. -- William Pursell

Re: hide object files

directory. -- William Pursell

[PATCH] Banner test for singletons.

skip-test || Exit 1 -- William Pursell

typo in comment in tests/defs.in

+ # This tool always wants to do something (by default # it will try link *nothing* and complain it cannot find # main(); funny). Use -help so it does not try linking anything. echo $me: running $CC -V -help -- William Pursell

error building ac378dbab6 on mac os X

/Makefile.in] Error 1 -- William Pursell

Fixing plural case in Banner

Here's a patch to prevent that grammatically incorrect text: All 1 tests passed Unfortunately, I haven't been able to build automake, so I cut-and-pasted from here into a Makefile to check the syntax. It's a pretty simple patch, and hopefully I haven't flubbed it. -- William Pursell From

Re: error building ac378dbab6 on mac os X

Ralf Wildenhues wrote: Hello William, * William Pursell wrote on Thu, Oct 09, 2008 at 06:28:18PM CEST: bash-3.2$ make CDPATH=${ZSH_VERSION+.}: cd ../automake perllibdir=/Users/williampursell/git/build-automake/lib:./lib /Users/williampursell/git/build-automake/aclocal --acdir=m4 -I m4

Re: multiple targets, different build options

. -- William Pursell

Re: Small documentation issue

Ralf Wildenhues wrote: * NightStrike wrote on Sun, Jan 13, 2008 at 10:08:58AM CET: AC_INIT takes in parameters the name of the package, its version number, and a contact address for bugreports about the package (this address is output at the end of ./configure --help, for instance). That's

multi-line AC_SUBSTs as targets in Makefile.am

I've been using AC_SUBST_FILE to put common targets into my makefile.am's. eg, Makefile.am contains: @FOO_TARGET@ where configure.ac contains FOO_TARGET=foo_target AC_SUBST_FILE(FOO_TARGET) and foo_target contains: foo: echo foo I would like to do this via AC_SUBST, but this

Re: multi-line AC_SUBSTs as targets in Makefile.am

Andreas Schwab wrote: William Pursell [EMAIL PROTECTED] writes: I'd like to get away from AC_SUBST_FILE, but I don't see a way around the manner in which automake is building the Makefile. Is there a way to construct a generic target via AC_SUBST? How about using AM_CONDITIONAL instead