powerpc-ibm-aix7.1.5.0 (with XPG_SUS_ENV=ON)
> powerpc-ibm-aix7.3.1.0 (with XPG_SUS_ENV=ON)
Same results as above on
i686-unknown-sysv5UnixWare7.1.4
i686-unknown-sysv5SCO_SV6.0.0
i686-pc-sco3.2v5.0.7
x86_64-unknown-freebsd10.1
--
Tim RiceMultitalents
t...@multitalents.net
macros
> macOS: self-contained
> mingw: self-contained
> Minix: self-contained
> musl: self-contained
> NetBSD: self-contained
> OpenBSD: self-contained
> Solaris 10: #include -> #include ,
> #include , defines only macros
> Solaris 11: #includ
nd configure
was just as happy as before. Like Solaris /bin/sh, UniWare's does
not handle $(...) either.
--
Tim RiceMultitalents
t...@multitalents.net
e shell and exec(ing) itself, then that is
not so good.
> % jsh config.sub x86_64-pc-linux-gnu
> config.sub: syntax error at line 53: `me=$' unexpected
>
> (The heirloom-sh is essentially Solaris /bin/sh but runs on GNU/Linux
> systems).
--
Tim RiceMultitalents
t...@multitalents.net
Forget to "rm -r autom4te.cache" ?
--
Tim RiceMultitalents
t...@multitalents.net
be wrong and configure scripts could be used ten years
> later without being re-generated with the latest rules.
Agreed.
An example is xz-5.0.5. Configure errors out complaining of no c99 compiler
but after fooling configure the package builds fine using a c
t; /dev/null 2>&1; then
>
> fi
"if ! test ..." is definitely not portable.
>
> This works also when something else than a number or nothing at all is given.
>
> I will try to remember autoconf also eats brackets.
>
> arie
--
Tim Rice
;
> +#include ]])
>
>
> After the command: aclocal $ACLOCAL_FLAGS -I . with configure.ac, the failure
> output is as followed:
>
> configure.ac:164: error: AC_CHECK_MEMBER: requires literal arguments
Try
AC_CHECK_MEMBERS([struct ifaddrs.ifa_addr-&g
ma-utils.
>
> so do you have any other distros to list ?
> -mike
UnixWare, OpenServer 5 & 6
--
Tim RiceMultitalents
t...@multitalents.net
___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf
On Tue, 3 Aug 2010, Eric Blake wrote:
> On 08/03/2010 04:37 PM, Tim Rice wrote:
> >>> What version of ksh did you test on?
> >> My testing was with ksh93:
> >> Version M 1993-12-28 o+
> >>
> >> So David Korn introduced a regression sometime sinc
On Tue, 3 Aug 2010, Eric Blake wrote:
> On 08/03/2010 03:42 PM, Tim Rice wrote:
> >> ksh is the only shell that requires a space between the ) and {, even
> >> though the ) is a metacharacter and should not need trailing space (even
> >> Solaris /bin/sh got th
s Version M-11/16/88h
On my Solaris 10 box with ksh Version M-11/16/88i
$ ksh -c 'a(){ echo hi; }; a'
hi
Even my old OpenLinux 3.1.1 machine running pdksh-5.2.14-6MR gets it right
What version of ksh did you test on?
--
Tim RiceMultitalents(707) 88
example. I was merely trying to make sure John had considered
the case of multiple config.h in a project. I think that is what Bob
was saying.
>
> H
--
Tim RiceMultitalents(707) 887-1469
t...@multitalents.net
_
radutmp/config.h.in
src/modules/rlm_smb/config.h.in
src/modules/rlm_smsotp/config.h.in
src/modules/rlm_sql/drivers/rlm_sql_mysql/config.h.in
src/modules/rlm_sqlhpwippool/config.h.in
src/modules/rlm_unix/config.h.in
It would work to have each of those with
#ifndef FREERADIUS
rsion M-11/16/88h) on both UnixWare
machines and all tests pass. This kind of suprised me. In times past ksh88
would give me more grief than ksh with autoconf.
All in all things are quite improved over 2.64 and 2.65.
--
Tim RiceMultitalents(707) 887-
ot in coreutils, the pattern
"1define" is only in configure and can also be found in
autoconf-2.59c/lib/autoconf/status.m4
--
Tim RiceMultitalents(707) 887-1469
[EMAIL PROTECTED]
16 matches
Mail list logo
