If you're interested in porting to Solaris 10, I suggest reading the
Autoconf documentation, which talks about the various pitfalls of
Solaris 10's multiple implementation of awk, sh, grep, etc. See:
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.72/html_node/Portable-Sh
On Mon, Sep 16, 2024 at 03:29:58AM +, Peter Gutmann via cfarm-users wrote:
> Thorsten Glaser via cfarm-users writes:
>
> >So, please keep it that way ;-)
>
> +1. Having access to a very diverse range of compilers and build
> environments, even if some are broken-by-design from the vendor, i
Thorsten Glaser via cfarm-users writes:
>So, please keep it that way ;-)
+1. Having access to a very diverse range of compilers and build
environments, even if some are broken-by-design from the vendor, is extremely
useful both to shake out bugs and for regression testing on older systems.
x86-
On Sun, 15 Sep 2024, Jacob Bachmeyer via cfarm-users wrote:
> I think that there *is* a POSIX shell on Solaris 10, it is just that /bin/sh
> is
> not that shell. I just checked and running "PATH=`getconf PATH` command -v
> sh"
Incidentally, I registred with the compile farm precisely to test
t
Denis Ovsienko via cfarm-users wrote:
On Sun, 15 Sep 2024 15:39:18 +
Peter Gutmann via cfarm-users wrote:
(OK, it's not quite that bad, but several things are pre-Posix at
least, e.g. /bin/sh doesn't understand "$(...)" but requires `...`).
I ran into this particular thing after
