Hi Bruno,
On 7/8/11 5:24 PM, Bruno Haible wrote:
+If you are using GNU @code{automake} 1.10 or newer, it is even easier:
+Add the line
+
+@example
+ACLOCAL_AMFLAGS = --install -I m4
+@end example
+
+@noindent
+to your top level @file{Makefile.am}, and run @samp{aclocal --install -I m4}.
+This
Hello,
On an FHS-style system, all macros are picked up from
/usr/share/aclocal. Conversely, on a Stow/Nix-style installation,
macros are to be found in /foo/automake/share/aclocal,
/bar/guile/share/aclocal, /baz/pkg-config/share/aclocal, etc.
It seems to me that the latter calls for user
tags 9026 patch
thanks
On Friday 08 July 2011, Ludovic Courtès wrote:
Hello,
Hi Ludovic, thanks for the report.
On an FHS-style system, all macros are picked up from
/usr/share/aclocal. Conversely, on a Stow/Nix-style installation,
macros are to be found in /foo/automake/share/aclocal,
Ludovic Courtès wrote:
... having a reproducible way of
producing tarballs, and user-specific environment settings appear to go
counter this goal.
Not only that. Also, it is important for distributors to be able to
regenerate the 'configure' file of packages, for a variety of reasons.
They can
Hi Bruno.
On Friday 08 July 2011, Bruno Haible wrote:
Ludovic Courtès wrote:
... having a reproducible way of
producing tarballs, and user-specific environment settings appear to go
counter this goal.
Not only that. Also, it is important for distributors to be able to
regenerate the
Hi Stefano,
I say we should instead follow the UNIX practice of giving the user enough
rope to hang himself, but advise him not to do so
This is a good attitude for the many features with which a developer can
only harm himself and which cause no harm to others.
But with $ACLOCAL_PATH he can
Hi Stefano,
Also, a conscientious user would anyway add
`--install -I m4' to his ACLOCAL_AMFLAGS, so that third-party m4 files
would be copied in the local m4 directory (and thus automatically
distributed by automake).
Hey, the --install option is something I need to mention in the GNU
