Re: FYI: AM_PROG_REGEX was broken

Pavel> I have checked (manually) all Automake *.m4 files for Pavel> underquoting. AM_PROG_REGEX was actually broken. Now it's Pavel> fixed. Thanks. Tom

Re: automake version 1.5 : when ?

> "Benoit" == benoit LOOF <[EMAIL PROTECTED]> writes: Benoit> Does anybody know when automake 1.5 will be available ? Nobody knows. Tom

Re: How to perform Automatic dependency tracking when compiling with cc ?

> "Benoit" == benoit LOOF <[EMAIL PROTECTED]> writes: Benoit>* i need to generate makefiles that compile my program using cc Benoit>* automake 1.4 requires gcc to perform Automatic dependency tracking Benoit> so my question is : how to get the benefits of Automatic Benoit> dependency

Re: Wanting to checkout cvs automake

> "Tim" == Tim Heath <[EMAIL PROTECTED]> writes: Tim>I execute the command with the following output: Tim> cvs -z 9 -d :pserver:[EMAIL PROTECTED]:/cvs/automake login Tim> (Logging in to [EMAIL PROTECTED]) Tim> CVS password: Tim> cvs [login aborted]: connect to anoncvs.cygnus.com:2401 fail

Re: variable substitution in AC_OUTPUT

> "Marc" == Marc van Woerkom <[EMAIL PROTECTED]> writes: Marc> MY_MODULES="Base Dataserver2" Marc> MY_MAKEFILES="`for D in $MY_MODULES; do echo $ac_n ' '$D/Makefile; done`" Marc> AC_OUTPUT([ Marc> Makefile Marc> macros/Makefile Marc> $MY_MAKEFILES Marc> src/Makef

Re: libraries built from subdirectories

> "Marc" == Marc van Woerkom <[EMAIL PROTECTED]> writes: >> This is possible with the cvs automake. Marc> Has the different behaviour between 1.4 and 1.4a (cvs automake) Marc> been documented anywhere? Nope :-(. Sometimes we've updated the docs but sometimes we haven't. (Where "we" usually

Re: Attempting to unit test

> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: >> Do you think it would be better to warn or to simply recognize >> lines like that? Pavel> I think it's better to recognize those lines and ignore Pavel> spaces. Doing otherwise will make Automake somewhat similar to Pavel> Python becau

Re: More fun with BUILT_SOURCES

> "Braden" == Braden McDaniel <[EMAIL PROTECTED]> writes: >> > I realize that BUILT_SOURCES is known to be problematic, but I haven't >> > found any other solution. Any suggestions? >> Add explicit dependencies on it. There's no other way to ensure it's >> generated. BUILT_SOURCES used to

Re: [Fwd: --add-missing]

> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes: Derek> Yep. Looks like that could be used by configure to set, say, Derek> TEX_TEXINPUTS & PDFTEX_TEXINPUTS and prepend include dirs Derek> differently for different targets, but I suspect that if your Derek> TeX distribution includes kp

Re: More fun with BUILT_SOURCES

On 25 Nov 2000, Tom Tromey wrote: > > "Braden" == Braden McDaniel <[EMAIL PROTECTED]> writes: > > >> > I realize that BUILT_SOURCES is known to be problematic, but I haven't > >> > found any other solution. Any suggestions? > > >> Add explicit dependencies on it. There's no other way to ensu

Re: Unusual directory structure

> "Fred" == F Labrosse <[EMAIL PROTECTED]> writes: Fred> I found a way to do all that. My only whish, for now, is that I Fred> would like to have a new kind of target: OBJECTS to only build Fred> .o files and not complete programs or libraries. Can you Fred> comment on that? There have bee

Re: rpath command?

>> Do I have to use some macro in configure.in to fill $(LINK) with GNU ld? Alexandre> automake should define it to `$(LIBTOOL) $(CC/CXX)...'. Alexandre> Maybe it only does this when there is at least one source Alexandre> file to compile in the current directory? Yeah, that's how it works. I r