Hi Bruno,
On Wed, Sep 15, 2010 at 11:18 AM, Bruno Haible <br...@clisp.org> wrote:
> Have you tried to follow the approach of
> <http://www.gnu.org/software/gnulib/manual/html_node/POSIX-Substitutes-Library.html>?
I have now.
> I haven't, but I would like to hear about success or problems that
> you encounter.
Notice from module atexit:
This module is obsolete.
Notice from module error:
If you are using GNU gettext version 0.16.1 or older, add the
following options
to XGETTEXT_OPTIONS in your po/Makevars:
--flag=error:3:c-format --flag=error_at_line:5:c-format
Notice from module fnmatch-posix:
This module is obsolete. Use the module 'fnmatch' instead.
Notice from module free:
This module is obsolete.
Notice from module localcharset:
If your package's tests make use of the locale_charset() function directly or
indirectly, you may need to define the CHARSETALIASDIR environment variable,
so that "make check" works before "make install". In Makefile.am syntax:
TESTS_ENVIRONMENT += @LOCALCHARSET_TESTS_ENVIRONMENT@
Notice from module memcmp:
This module is obsolete.
Notice from module memcpy:
This module is obsolete.
Notice from module memmove:
This module is obsolete.
Notice from module memset:
This module is obsolete.
Notice from module raise:
This module is obsolete.
Notice from module strcspn:
This module is obsolete.
Notice from module strdup:
This module is obsolete. But you may want to use the strdup-posix module.
Notice from module strpbrk:
This module is obsolete.
This sounds like something I've said before: Should recommended procedures
*not* trigger "this is obsolete" type messages? (sharutils also runs into these
messages because of cascaded dependencies requiring obsolete stuff.)
This is all I noticed out of the three thousand four hundred odd lines
of output.
That is very impressive and impossible to eyeball parse.
