> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
Harlan> Since I have not found a way to tell the various people who
Harlan> work on autoconf that a particular date or tag of the autoconf
Harlan> tree is what they have to use, I simply keep a tarball around
Harlan> of the version I am u
| NTP, on the other hand, appeared to be using *some* 2.14a version of
| autoconf. But it's hard to determine really as there are no periodic
| checkpoints or at least tie in something to indicate which code set things
| were built with.
Right, this is another perverse effect of the long delays
The NTP project is using an "older" version of the CVS autoconf.
One of the differences between the newer and older versions of autoconf is
"how do you specify the list of members to AC_CHECK_MEMBERS?"
Since I have not found a way to tell the various people who work on autoconf
that a particula
On Tue, Jun 27, 2000 at 09:30:09PM -0700, Mo DeJong wrote:
> > So I guess this is an improvement. One problem at a time.
> >
> > However, I must say, I do NOT like it changing "i386-linux" to
> > "i386-pc-linux-gnu". That is not what I typed in. If I want to override
> > it, I want to damn wel
> So I guess this is an improvement. One problem at a time.
>
> However, I must say, I do NOT like it changing "i386-linux" to
> "i386-pc-linux-gnu". That is not what I typed in. If I want to override
> it, I want to damn well override it.
>
> mrc
Did you try "./configure --build=i386-linux"
Replying to list.
The specific packages I was having problems with were lesstif and ntp.
Harlan Stenn working on the ntp package has posted here recently (I've
already lost track of these thread on autoconf).
In particular, lesstif was using 2.14.1 (I'm guessing the branch
autoconf-2-15-branch,
