open in hopes of figuring out that m4 stub
> approach, but this is all I can see to do for the 1.17 release. (I've
> got nothing else pending for 1.17, so if anyone knows of a reason to
> delay, let me know asap.) --thanks, karl.
>
This looks great, Karl, thanks for all your time investigating and
documenting the issue. Lots of nice nit-fixing too!
Cheers,
Dave Hart
issue on the automake mailing list
would be productive in terms of soliciting suggestions on how to implement
this corner case improvement.
Meanwhile, I'll at least tweak the (test relese) NEWS and error message
> as you suggested. --thanks, karl.
>
Thank you.
--
Cheers,
Dave Hart
On Wed, 3 Jul 2024 at 19:52, Nick Bowler wrote:
> On 2024-07-03 09:37, Dave Hart wrote:
> > On Wed, 3 Jul 2024 at 03:49, Dave Hart wrote:
> > > It occurs to me we might avoid issues along these lines by having
> > > our bootstrap script invoke libtoolize before auto
On Wed, 3 Jul 2024 at 03:49, Dave Hart wrote:
>
> It occurs to me we might avoid issues along these lines by having our
> bootstrap script invoke libtoolize before autoreconf. Does that sound wise
> to the two of you?
>
I tried this approach and it didn't help. libtooli
ly some real
> change in aclocal behaviour which is causing the results you are seeing.
>
Yes, and it's always good to understand these sorts of potential
regressions, but it might not justify more investigation given other
productive uses of volunteer developers' time if others aren't seeing it.
--
Cheers,
Dave Hart
release announcements should mention the issue somehow
(e.g. suggesting also installing libtool to any test prefix, or pointing
via 'autoreconf -d' or the environment variable).
B) Perhaps the libtool macros not found error message could hint at this
cause alongside the stuff about ensuring LT_INIT is used.
Thanks again,
Dave Hart
usr/local/bin earlier on $PATH
It might be something about the libevent configure.ac or Makefille.am, the
source tree has projects nested three deep:
configure.ac
sntp/configure.ac
sntp/libevent/configure.ac
If you are willing to spend some time, I'm guessing you could reproduce the
failure. Thanks for taking an interest.
Cheers,
Dave Hart
Nick Bowler helped educate me on aclocal and libtool interaction on the
Automake mailing list. The reason I was hitting this problem was aclocal
was not finding libtool installed to the same prefix as automake. To test
the prerelease automake I was leaving the base version of automake
installed a
x27; is in 'configure.ac', make sure
+Makefile.am:161: its definition is in aclocal's search path.
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
-autoreconf: Leaving directory 'libevent'
-autoreconf: running: libtoolize --copy
[...]
-ls: invalid tab size: './aclocal.m4'
+autoreconf: error: automake failed with exit status: 1
--
Cheers,
Dave Hart
bootstrap-am-1.16.5.log
Description: Binary data
bootstrap-am-1.16.92.log
Description: Binary data
Stefano,
In the proposed patch, the word "foo" is used where "force' was
apparently intended.
Without unwarranted aggressivity,
Dave Hart
When invoked by autoreconf of a project with nested configure.ac
files, automake does not respect the disabling of AC_CONFIG_FILES by
the top-level configure.ac using AM_COND_IF, resulting in an incorrect
Makefile. Re-running autoreconf from within the nested project
produces correct output.
http
12 matches
Mail list logo
