On Sat, May 06, 2000 at 12:35:34AM -0400, Pavel Roskin wrote:
> Hello!
Hey there.
> The current Libtool from CVS (head version) fails when I run configure:
>
> ltconfig: you must specify a host type if you use `--no-verify'
>
> It turns out that the following code from libtool.m4 is at fault:
I didn't want to cross-post. I also sent this message to one of the
software carpentry contest lists. Occasionally I remember my days of
Metaconf hacking, and believe it or not there is still something to
learn from that tool.
> "Greg" == <[EMAIL PROTECTED]> writes:
Greg> One of the thin
On May 6, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
> On Sat, May 06, 2000 at 12:35:34AM -0400, Pavel Roskin wrote:
>> It turns out that the following code from libtool.m4 is at fault:
>>
>> case "$target" in
Yup, it's all wrong. Libtool shouldn't care about the target, only
about th
On May 5, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> AC_DEFINE(UNIX_FILE_SYSTEM)
> will not actually add the #define to config.h.in.
It's not supposed to do it. Only the 3-argument version of AC_DEFINE
causes autoheader to add something to config.h.in. But it's not clear
to me what's The R
On May 6, 2000, Tom Tromey <[EMAIL PROTECTED]> wrote:
>> "Greg" == <[EMAIL PROTECTED]> writes:
Greg> One of the things that I find frustrating in 'autoconf' is that
Greg> dependencies between configuration tests are not explicit.
> FWIW: this is one of the things that Metaconf (the packa
Metaconf uses the concept of "Unit" files (similar to an autoconf macro).
When designing a package that uses metaconf, one just lists the "pieces" one
needs, and the generator takes these things and (using "make -n", as I
recall), finds all of the prerequisites, orders the tests, anad produces a
