On Wed, 3 Jul 2024 at 00:58, Nick Bowler wrote:
> For autoreconf to work with libtool there just needs to be a definition
> of LT_INIT available when it runs autoconf for the first time, in order
> for the traces to indicate an expansion of LT_INIT. There are a variety
> of ways this might happe
On 2024-07-02 13:34, Dave Hart wrote:
> Thanks for running this down, Karl. I'm happy if you're happy, but I
> am left with one question: Why is it installing prerelease automake
> in a different prefix for testing hasn't required also installing
> libtool to the same prefix (think back to your "
Hi Dave,
Why is it installing prerelease automake in a different prefix for
testing hasn't required also installing libtool to the same prefix
In general, I think it does. And always has. This is not new behavior,
as far as I can see.
(think back to your "baffled" comment)?
Indeed :
On Tue, 2 Jul 2024 at 17:15, Karl Berry wrote:
> Hi Dave,
>
> # wget https://davehart.net/ntp/test/ntp-4.2.8p18-vcs.tar.xz
> # tar xf *p18-vcs*xz
> # cd *vcs
> # ./bootstrap
>
> After more testing, I don't believe it is a regression. If I install
> 1.16.5 in its own prefix, say /t
Hi Dave,
# wget https://davehart.net/ntp/test/ntp-4.2.8p18-vcs.tar.xz
# tar xf *p18-vcs*xz
# cd *vcs
# ./bootstrap
After more testing, I don't believe it is a regression. If I install
1.16.5 in its own prefix, say /tmp/am165, the ntp bootstrap fails in the
same way:
Makefile.am:16
