[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gettext patches for cygwin #2: autoconf warnings, cygwin/getopt

From: Bruno Haible
Subject: Re: gettext patches for cygwin #2: autoconf warnings, cygwin/getopt
Date: Tue, 22 Nov 2005 12:55:51 +0100
User-agent: KMail/1.5

Charles Wilson wrote:
> +case $host in
> +  dnl On cygwin and mingw, the system getopt is hardcoded to use
> +  dnl POSIXLY_CORRECT -- which causes some gettext selftests to fail.
> +  dnl Therefore, we always use the replacement version (symbol clash
> +  dnl avoided because gnulib redefines the names to rpl_*)
> +  *cygwin* | *mingw* ) gl_GETOPT_SUBSTITUTE ;;
> +esac

Actually, the gettext testsuite is buggy. I've now made the testsuite
work with "env POSIXLY_CORRECT=1 make check". So it is not needed any
more to use GNU getopt if the system already has a fully POSIX compliant
getopt() and getopt_long().

If a system does not support the GNU extension which allows to put
option arguments after non-option arguments, it's a choice of the system's
architects. (It has an effect on users, who must tediously port their
shell scripts, reordering arguments in command invocations. But on the
standards side, there's nothing to say against it.) GNU gettext follows
this choice of the platform architects, by using the platform-provided


reply via email to

[Prev in Thread] Current Thread [Next in Thread]