Re: How to specify /var/lib in autoconf?

Hello, * Eric Blake wrote on Wed, May 13, 2009 at 02:21:36PM CEST: > [moving to bug-automake] FWIW, moving isn't practical if the original reporter isn't kept in Cc:. > According to Eric Blake on 4/24/2009 9:48 AM: > > David Bruce writes: > > > >>> AM_CPPFLAGS = -DLOCALSTATEDIR=\"$(pkglocalsta

Re: make -s & libtool

Hello Samuel, * Samuel Thibault wrote on Tue, May 12, 2009 at 05:56:49PM CEST: > I usually use make -s to better see warnings. However, libtool echoes > the commands... Automake's autogenerated Makefile.in should check for > the presence of -s in MAKEFLAGS, and in that case pass --silent to > li

Re: How to specify /var/lib in autoconf?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [moving to bug-automake] According to Eric Blake on 4/24/2009 9:48 AM: > David Bruce gmail.com> writes: > >>> If you want to refer to the path in C code as a macro "LOCALSTATEDIR", >>> you have in Makefile.am: >>> >>> AM_CPPFLAGS = -DLOCALSTATEDIR=

AM_PROG_GCJ fails at `make' if nothing else defines OBJEXT

Hi list, I've found that if nothing else defines OBJEXT, AM_PROG_GCJ won't do it and then make will fail with an error like: make: *** No rule to make target `Test.', needed by `test'. Stop. Minimal complete example (I'm using autoconf 2.63 and automake 1.10.2): configure.ac: 8<--- AC_INIT([

make -s & libtool

Hello, I usually use make -s to better see warnings. However, libtool echoes the commands... Automake's autogenerated Makefile.in should check for the presence of -s in MAKEFLAGS, and in that case pass --silent to libtool. Samuel (please Cc me)