Mikhail Teterin <[EMAIL PROTECTED]> writes: > I see -- would you have a test-case, that detects this difference?
No, but you can read the thread containing this message: http://lists.gnu.org/archive/html/bug-gnulib/2004-10/msg00171.html to see some of the issues here, and why gnulib getopt.m4 rejects BSD's emulation of GNU getopt. > cvs -z 9 -d :pserver:[EMAIL PROTECTED]:/cvs/glibc \ > co -r fedora-glibc-2_3_4-21 libc/posix libc/include > > As before, are there tests, that detect incompatibilities? There we have quite a few more tests; see <http://cvs.savannah.gnu.org/viewcvs/*checkout*/gnulib/m4/regex.m4?root=gnulib>. Even glibc doesn't satisfy the current tests, so there's no shame in your failing them too. I'm working on getting glibc fixed, but these things take time. (To some extent its an arms-race problem as we can add tests faster than the libc maintainers can fix the regex bugs.... :-) You can try them out by downloading, say <ftp://alpha.gnu.org/gnu/coreutils/coreutils-6.2.tar.bz2>, configuring with LIBS=-lgnuregex or whatever magic you like, and then seeing whether 'configure' decides to use your regex implementation. If it works, I suppose we can try to automate adding the linker magic and put that into regex.m4. But I can't resist asking: why can't the BSD folks just make a gnulib-compatible regex be the default? That would make life easier for lots of people.
