Re: mingw and memcmp

2007-12-21 Thread Paul Eggert
Bruno Haible <[EMAIL PROTECTED]> writes: > - You can bury the 'memcmp' module. It's not needed by ANSI C systems, > and gnulib assumes ANSI C for ca. 2 years already. I think we're assuming freestanding C89 or better, right? memcmp is required for hosted C89, but not for freestanding. It's

m4 and progname (was: Re: mingw and memcmp)

2007-12-21 Thread Bruno Haible
Eric Blake wrote: > (I'm starting to wonder if it is easier to require all test-foo.c programs to > declare and populate program_name themselves, rather than relying on the > progname module.) Oh no. The progname module is there to simplify things for both programs and test suite. It would be b

Re: mingw and memcmp

2007-12-21 Thread Bruno Haible
Hi Eric, > +2007-12-20 Eric Blake <[EMAIL PROTECTED]> > + > + Work around circular library issue when cross-compiling. > + * lib/progname.c (set_program_name): Use strncmp, not memcmp, so > + that progname.o does not need to pull in rpl_memcmp. I don't like this patch at all.

mingw and memcmp

2007-12-20 Thread Eric Blake
I ran into this build failure in m4 when cross-compiling to mingw: gcc -mno-cygwin -std=gnu99 -gdwarf-2 -Wall -Werror -o test-avltree_oset.exe test-avltree_oset.o libtests.a ../lib/libm4.a libtests.a libtests.a(progname.o): In function `set_program_name': ../../tests/progname.c:44: undefin