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, but not certain). [Btw, I somewhat suggested
checking out that branch to Harlan, which I not see was a mistake. Sorry!]
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.
Anyway, if I take ntp 4.0.99j out of the box, I get this:
nexus@thune[10:41pm]src/ntp/ntp-4.0.99j(576) ./configure i386-linux
creating cache ./config.cache
checking host system type... i386-pc-linux-gnu
checking target system type... i386-pc-linux-gnu
checking build system type... i386-pc-linux-gnu
configure: error: can only configure for one host and one target at a time
If I run the latest autoconf (with just "autoconf", not sure if I should be
doing more; I'm very new to this). Then run the resultant configure, I
get past the non-opt portion, but break later:
nexus@thune[10:43pm]src/ntp/ntp-4.0.99j(580) ./configure i386-linux
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: i386-linux
checking build system type... i386-pc-linux-gnu
checking host system type... i386-pc-linux-gnu
checking target system type... i386-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
[deleted]
checking if we have support for PARSE clocks... yes
checking if we have support for audio clocks... no
checking for (struct audio_info.monitor_gain,
struct audio_info.output_muted,
struct audio_info.blocksize,
struct audio_info.hiwat,
struct audio_info.lowat,
struct audio_info.mode)... no
./configure: line 9501: syntax error near unexpected token `audio_info'.)'
./configure: line 9501: ` struct audio_info'.)'
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
On Mon, Jun 26, 2000 at 10:39:47AM +0200, Akim Demaille wrote:
> >>>>> "Mike" == Mike Castle <[EMAIL PROTECTED]> writes:
>
> Mike> In article <[EMAIL PROTECTED]> you write:
> >>>>>>> "Mike" == Mike Castle <[EMAIL PROTECTED]> writes:
> Mike> AC_CANONICAL_SYSTEM v AC_CANONICAL_HOST.
> >> Drop Autoconf 2.13 dead in this area. Its design for
> >> AC_CANONICAL_* is unclear, unpredictable etc. The current CVS
> >> version of Autoconf has a more formal approach which should be
> >> clearer and easier to understand.
>
> Mike> I'm not a developer using configure. I'm an end user
> Mike> experiencing problems with developers who are using 2.14.1. It
> Mike> appears, from my point of view, to be broken.
>
> Mike> ./configure non-opt-host
>
> Mike> Does NOT work when _SYSTEM is used.
>
> Mike> If it's designed that way, the documentation needs to be
> Mike> updated, and the non-opt stuff removed from ./configure --help
> Mike> (and possibly INSTALL).
>
> Did you use the CVS version? Because it works, and it is undocumented.
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
