Hello Harlan,
On Wed, Sep 21, 2005 at 10:05:51AM +, Harlan Stenn wrote:
> > So if you run automake in both of these projects, both runs will
> > generate sntp/libopts/Makefile.in.
>
> Yes, which I agree is probably wrong,
it is wrong.
> but at this time I want to allow people to build ntp a
Hi Stepan,
> here is an explanation of your problem: sntp/libopts is a subdir
> of both of the packages: ntp-4.0.2b and ntp-4.0.2b/sntp.
Yes...
> So if you run automake in both of these projects, both runs will
> generate sntp/libopts/Makefile.in.
Yes, which I agree is probably wrong, but at th
Hello Harlan,
here is an explanation of your problem: sntp/libopts is a subdir
of both of the packages: ntp-4.0.2b and ntp-4.0.2b/sntp.
So if you run automake in both of these projects, both runs will
generate sntp/libopts/Makefile.in.
Well, this is consitent with the fact that both ./configure a
Hi Stepan,
> I tried this with ntp-dev-4.2.0b-20050917 and saw nothing suspicious:
That's because I have not yet released this code.
If you visit http://ntp.isc.org/~stenn you'll see a tarball.
I believe you will have to run:
% autoreconf -vfi
in the top-level directory to get it back to th
Hello Harlan,
On Mon, Sep 19, 2005 at 08:34:43PM +, Harlan Stenn wrote:
> If I go to the top of the tree and run "autoreconf -vfi" the resulting
> Makefile.in files under sntp/ fail because they contain generated
> dependencies for .m4 files from ntp's m4/ subdir that are both not
> needed and
I'm not sure what portion of this issue is automake, and what portion is
autoconf.
NTP is a "nested" auto* package. It contains a subpackage, sntp, which
is designed to be separable from the rest of the tree.
This means that if a library is needed by both "trees", I put it as a
subdir under ntp/
