variables in _SOURCES

According to the "Warning" in this page[1], it is not permitted to use variables in _SOURCES. Is this deliberate or is it a bug? In our project, we started getting the warnings about subdir-objects and so we added[2] AM_INIT_AUTOMAKE([foreign subdir-objects]) However, since that time the bu

appending LDADD to prog_LDADD

I understand from the docs that specifying prog_LDADD will override LDADD (and the same for prog_CPPFLAGS, ...) http://www.gnu.org/software/automake/manual/html_node/Linking.html If it is desired to merge prog_LDADD and LDADD, is there any recommended or preferred solution? I've tried

only installing shared versions of some libs

I've recently adapted a project to support DSO plugins/modules The existing project includes normal libraries and binaries. In a normal build, we want to a) build and install the shared and static versions of the normal libraries b) only install the shared versions of the plugins I don't min

make dist for both Debian and Fedora?

Hi, I use a Debian system to run autoreconf and bootstrap/make dist releases for various projects (e.g. reSIProcate) When using the release tarball on a system like Fedora, issues with hard-coded rpath have been discovered. Apparently I am not alone, and this discussion has come up before in RP

Re: AIX shared libraries, make install misses them

Ralf Wildenhues wrote: Hello Michael, * Michael Perzl wrote on Fri, Jan 29, 2010 at 07:46:57PM CET: That is without the "-Wl,-brtl" passed to LDFLAGS, so libtool is behaving correctly on AIX to put the modcpu.so into the modcpu.a library archive. The "misbehavior" is that the "*.a" containi

Re: AIX shared libraries, make install misses them

Ralf Wildenhues wrote: Hello Michael, * Michael Perzl wrote on Fri, Jan 29, 2010 at 07:46:57PM CET: That is without the "-Wl,-brtl" passed to LDFLAGS, so libtool is behaving correctly on AIX to put the modcpu.so into the modcpu.a library archive. The "misbehavior" is that the "*.a" containi

Re: AIX shared libraries, make install misses them

Daniel Pocock wrote: Ralf Wildenhues wrote: Hello Daniel, * Daniel Pocock wrote on Thu, Jan 28, 2010 at 03:21:24PM CET: We have been working on getting the Ganglia tarball to work out of the box for AIX When Michael does `make install', the *.so files for our modules ar

Re: AIX shared libraries, make install misses them

Ralf Wildenhues wrote: Hello Daniel, * Daniel Pocock wrote on Thu, Jan 28, 2010 at 03:21:24PM CET: We have been working on getting the Ganglia tarball to work out of the box for AIX When Michael does `make install', the *.so files for our modules are not installed. Instea

Re: AIX shared libraries, make install misses them

Daniel Pocock wrote: We have been working on getting the Ganglia tarball to work out of the box for AIX The tarball is bootstrapped using autotools on Debian 5. When Michael does `make install', the *.so files for our modules are not installed. Instead, he sees output like this

AIX shared libraries, make install misses them

We have been working on getting the Ganglia tarball to work out of the box for AIX The tarball is bootstrapped using autotools on Debian 5. When Michael does `make install', the *.so files for our modules are not installed. Instead, he sees output like this from `make install': -

Re: AIX linking: -berok in aclocal.m4 and libtool

Ralf Wildenhues wrote: Hello Daniel, * Daniel Pocock wrote on Sat, Jan 16, 2010 at 02:09:55PM CET: Could anyone share any advice on using autoconf and automake to prepare a distribution tarball that will work on AIX? Normally, I build the tarball on Linux (Debian 5). The AIX users need to

AIX linking: -berok in aclocal.m4 and libtool

Hi, Could anyone share any advice on using autoconf and automake to prepare a distribution tarball that will work on AIX? Normally, I build the tarball on Linux (Debian 5). The AIX users need to be able to use the tarball to build an executable (gmond), a static library (libmetrics) and

Re: making config files

You probably mean $(top_builddir) Thanks - I'll fix that one %: %.tmpl $(FIXCONFIG) $(FIXCONFIG) $< AFAIU, %: %.tmpl is GNU Make specific and won't work with other makes. I realised the same thing and took it out and put something like the following into each Makefile.am: include $(top

Re: making config files

Russ Allbery wrote: Daniel Pocock writes: Thanks for that - the sed example appears to be the type of thing I want. However, is there a more concise way to do this? I was thinking there may be some way to invoke sed or m4 on a template in much the way that gcc is invoked for

Re: making config files

Russ Allbery wrote: Daniel Pocock writes: Thanks for that - the sed example appears to be the type of thing I want. However, is there a more concise way to do this? I was thinking there may be some way to invoke sed or m4 on a template in much the way that gcc is invoked for

Re: making config files

Peter Johansson wrote: Daniel Pocock wrote: Therefore, I felt that I should be aiming to have the config files generated at the last moment - probably during `make install', just before they are installed. Can anyone suggest best practice for doing this? please refer to

making config files

Hi, I've been working on a project, Ganglia, that is built with autotools Included in the source tree are templates for various configuration files (e.g. modpython.conf.in). Some of these include hard coded paths. It seems appropriate to replace the hardcoded paths with substitutions (e.g