Fixes automake bug https://bugs.gnu.org/21547.
If users have interactive site file logic, the lispdir probing can
hang, as can the compilation of elisp files. Use --no-site-file to
disable loading any of that possible user logic.
* NEWS: Note emacs --no-site-file change.
* doc/automake.texi:
From: Mathieu Lirzin
Fixes automake bug https://bugs.gnu.org/30172.
Since AM_MAKEINFOHTMLFLAGS overrides AM_MAKEINFOFLAGS only for html
targets, make sure we restore the hacked up makefile before testing
the non-html formats. This normally doesn't cause a problem for most
people, but if their
On 19 Jan 2018 16:30, Mathieu Lirzin wrote:
> The test suite fails for “t/txinfo-many-output-formats.sh” and
> “t/txinfo-many-output-formats-vpath.sh”.
>
> $ make check \
> TESTS="t/txinfo-many-output-formats.sh
> t/txinfo-many-output-formats-vpath.sh"
>
> TEXINPUTS=".:$TEXINPUTS" \
>
On Fri, 09 Sep 2016 18:18:07 -0700, Michael Miller wrote:
> I recently had a problem building automake via Homebrew on OS X. Turns out
> the problem was that the path to Xcode contained a space: /Applications/Xcode
> 7.app \u2014 Removing the space caused the build to work correctly.
>
> To
We already invoke $AR with -NOLOGO all the time, so we can ignore the
option entirely if the user specifies it.
* lib/ar-lib: Ignore -NOLOGO.
---
lib/ar-lib | 4
1 file changed, 4 insertions(+)
diff --git a/lib/ar-lib b/lib/ar-lib
index 9dc8ef6df054..54c6bdbf7f1b 100755
--- a/lib/ar-lib
On 13 Mar 2019 20:23, Hans-Bernhard Bröker wrote:
> Am 13.03.2019 um 16:44 schrieb Allwright, James:
> > I believe I have found a bug in automake relating to the parsing of
> > filepaths and/or directories.
>
> I believe you have used automake incorrectly.
>
> > In proj3/ Makefile.am I have
>
On Tue, 13 Jan 2015 01:01:44 -0500, Daniel Richard G. wrote:
> I am building a source package, prepared with Automake 1.15, on HP-UX.
> While running the configure script, I get
>
> [...]
> config.status: creating include/Makefile
> config.status: creating scripts/Makefile
>
before i push, question about $scriptversion. is the policy for
handling these documented somewhere ? is it like m4 serial numbers
? it should be updated whenever there's a code change ?
Yes. Standard practice is to update scriptversion whenever a new version
of the file is
