>>>>> "Morten" == Morten Eriksen <[EMAIL PROTECTED]> writes:
>> Please, don't depend on this, it does not exist.
Morten> Guys, get your ass in gear and release a new version of
Morten> Autoconf, please -- so we don't have to live on the bleeding
Morten> edge.
:)
Morten> (Hey, just kidding.) :^}
Actually I just meant depend upon 2.14a.
>> | case "$host_os" in
>>
>> Where does this come from?
Morten> Hmm, from libtool's ltconfig. Could a host OS identifier be
Morten> found somewhere by using "standard" Autoconf features?
Checkout
- Macro: AC_CANONICAL_HOST
Perform only the subset of `AC_CANONICAL_SYSTEM' relevant to the
host type. This is all that is needed for programs that are not
part of a compiler toolchain.
System Type Variables
=====================
After calling `AC_CANONICAL_SYSTEM', the following output variables
contain the system type information. After `AC_CANONICAL_HOST', only
the `host' variables below are set.
``build', `host', `target''
the canonical system names;
``build_alias', `host_alias', `target_alias''
the names the user specified, or the canonical names if
`config.guess' was used;
``build_cpu', `build_vendor', `build_os''
``host_cpu', `host_vendor', `host_os''
``target_cpu', `target_vendor', `target_os''
the individual parts of the canonical names (for convenience).
Morten> I think I copied the idiom from the Autoconf sources, not
Morten> really knowing what I did. Lets see.. the same code is at
Morten> least used in AC_LIST_MEMBER_OF, in my checkout from the CVS
Morten> head from 2000-01-12.
Yes, and there are patches in the queue to remove this where useless :)
It is needed when $1 is the single command for the then or the else
part, since sh doesn't like empty clauses.
Akim
