Bug with conditionals. [PATCH]

2001-06-05 Thread Richard Boulton
I came across this problem a few days ago: just narrowed it down to a sensible test case. With CVS automake, if LDADD is set from both a conditional variable and an AC_SUBST() variable, the _DEPENDENCIES target gets set incorrectly, having a @TRUE@ preceding it (for each of the conditional variab

Re: The %.o: %.cc rule

2001-06-05 Thread Raja R Harinath
Tom Tromey <[EMAIL PROTECTED]> writes: >> "Hair" == Raja R Harinath <[EMAIL PROTECTED]> writes: >Clark> test_SOURCES = d1/s1.cc d2/s2.cc > >Hair> Try using >Hair> AUTOMAKE_OPTIONS = subdir-objects > > subdir-objects will cause Makefile to build d1/s1.o and d2/s2.o. > Without it, the above

Re: The %.o: %.cc rule

2001-06-05 Thread Clark Rawlins
Tom, Thanks for the guidance so far. I got automake and autoconf out of cvs and did ./configure --prefix=$HOME make test install on both projects autoconf first then automake and now I get some errors when I run aclocal and automake. %aclocal aclocal: configure.in: 10: macro `AM_PROG_LIBTOOL

auto generate -DLIBfoo_COMPILATION for libtool libraries

2001-06-05 Thread Robert Collins
The attached patch auto defines -DLIBfoo_COMPILATION in the _CFLAGS variable for libtool libraries. This is a proof of concept patch only, it's probably the wrong way to do it, there may be issues with always adding the define even if there are userland defines present. Consider this a request-to