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 autoreconf.
> [...]
> > I tried th
libtoolize: linking file `sntp/m4/libtool.m4'
Indeed, that seems like it should work, because the aclocal invocation
from autoreconf is looking into sntp/m4 (and /m4 too) and
finds other files there:
..
autoreconf: running: aclocal --verbose --verbose -I sntp/m4 -I sntp/libevent/m4
-I sntp/l
> But none of this is meant to suggest that there isn't actually some real
> change in aclocal behaviour which is causing the results you are seeing.
I've failed to find any regression. As I said, if I install 1.16.5 into
a test --prefix and run ntp's bootstrap with that prefix, it cannot
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 autoreconf.
[...]
> I tried this approach and it didn't help. libtoolize seems to be
> doin
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. libtoolize seems to be doing the
