Re: gnulib tests vs. LDADD

2007-04-16 Thread Eric Blake
Bruno Haible clisp.org> writes: > > It looks like gnulib needs to take its own advice when creating the Makefile.am > > for the tests directory, since I noticed the following message from gnulib- tool: > > Yes indeed. I'm committing this as an attempt to fix it. > > 2007-04-03 Bruno Haible

Re: gnulib tests vs. LDADD

2007-04-06 Thread Bruno Haible
This is needed as well: When the gettext module is present, the test programs indirectly rely on the gettext() function, therefore they must use @[EMAIL PROTECTED] But when the gettext module is not present, they must not link with -lintl - hence LIBINTL must be AC_SUBSTed with an empty value. 20

Re: gnulib tests vs. LDADD

2007-04-03 Thread Bruno Haible
Eric Blake wrote: > CVS findutils uses gnulib-tool --with-tests when importing. But on cygwin, > compilation then fails in the gnulib-created directory: > > gcc -g2 -Wall -Werror -o test-dirname.exe test- > dirname.o ../gnulib/lib/libgnulib.a > ../gnulib/lib/libgnulib.a(xalloc-die.o): In fun

Re: gnulib tests vs. LDADD

2007-04-03 Thread Bruno Haible
Eric Blake wrote: > I noticed the following message from gnulib-tool: > > You may need to use the following Makefile variables when linking. > Use them in _LDADD when linking a program, or > in _a_LDFLAGS or _la_LDFLAGS when linking a library. > $(LIB_CLOCK_GETTIME) > $(LTLIBINTL) when linking