-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding m4-discuss]
According to Bruno Haible on 5/27/2008 4:43 PM:
| Hi Eric,
|
| It seems that your problem is that you want execute a script via system()
| and at the same time force a particular shell, namely the $CONFIG_SHELL
found
| at configur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 5/27/2008 4:35 PM:
| Eric Blake wrote:
|> should m4/extensions.m4 blindly define
|> _POSIX_SOURCE for Solaris, like it already does for Minix
|
| Certainly not. On many systems, _POSIX_SOURCE *prevents* system
| extensions
Hi Eric,
It seems that your problem is that you want execute a script via system()
and at the same time force a particular shell, namely the $CONFIG_SHELL found
at configure time?
> $ gcc -o foo -Wall foo.c /usr/ccs/lib/values-xpg4.o
I would not use this approach for three reasons:
1) When you
Eric Blake wrote:
> should m4/extensions.m4 blindly define
> _POSIX_SOURCE for Solaris, like it already does for Minix
Certainly not. On many systems, _POSIX_SOURCE *prevents* system
extensions from being available. It's the opposite of _ALL_SOURCE (AIX),
_HPUX_SOURCE (HP-UX), _GNU_SOURCE (glibc)
Eric Blake byu.net> writes:
> But in my (limited) testing, I wasn't able to get that to
> happen with either gcc 3.3 or /usr/ucb/cc as the compiler and -
D_POSIX_SOURCE=1
> on the command line. Any ideas on how to select the standards-compliant
system
> (2) implementation on Solaris?
After r
I just debugged a failure of the m4 master branch testsuite on Solaris 8, and
tracked it to the fact that system(2) was using /bin/sh as its shell. The
Solaris documentation claims that defining _POSIX_SOURCE prior to including any
system headers will make system(2) use /bin/ksh instead, which
