> > I am afraid that being active maintainer asks for more time than I have
>
> That's quite understandable. I used SunOS 4 heavily, but
> it's now just a museum piece, and it doesn't appear to be
> worth your time or ours to maintain GNU utilities on it.
> (If the best way to run an environment is on an emulator,
> that's a good sign the environment is no longer real....)
To make things clear: "Active maintainer" means to make sure any new
version of gnulib runs perfectly on the system. I can't do that, but
I can send small patches to fix problems with SunOS that I apply anyway
to get certain packages using gnulib running for me, like grep. Where
can I send such patches?
So far, it did not take much for grep, m4 and gawk. Some examples:
--- grep-2.9/lib/hash.h 2011-04-14 09:33:10.000000000 +0200
+++ ./grep-2.9-hacked/lib/hash.h 2012-02-01 23:11:12.000000000 +0100
@@ -26,7 +26,7 @@
# include <stdio.h>
# include <stdbool.h>
-
+# include <stddef.h>
/* The __attribute__ feature is available in gcc versions 2.5 and later.
The warn_unused_result attribute appeared first in gcc-3.4.0. */
# if __GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 4)
--- grep-2.9/lib/version-etc.h 2011-04-14 09:33:10.000000000 +0200
+++ ./grep-2.9-hacked/lib/version-etc.h 2012-02-01 23:14:17.000000000 +0100
@@ -21,6 +21,7 @@
# include <stdarg.h>
# include <stdio.h>
+# include <stddef.h>
/* The `sentinel' attribute was added in gcc 4.0. */
#ifndef _GL_ATTRIBUTE_SENTINEL
Otherwise size_t is not declared. Then it would help an awful lot if
the check for a missing memmove could be put back in, along with memmove
itself.
A slightly more complicated issue is in src/dfa.c. The is* functions are
used, but they are macros on SunOS4 and if you undefine them (which is
not the case in src/dfa.c), you find there are no functions of the same
name in libc. In fact I am used to that from other older systems as well,
so making that more portable would be useful for others, too.
As for the meaning of SunOS 4: It is best described by hack value. :-)
Michael
