Re: test-string-c++ test failure

Jim Meyering wrote: > Bruno Haible wrote: > ... >> This should fix it: >> >> 2010-03-11 Bruno Haible >> >> Fix problems with overloaded C++ definitions of memchr, strpbrk, etc. >> * build-aux/c++defs.h (_GL_CXXALIAS_SYS_CAST2): Make it work regardless >> whether the system provid

Re: C++ libtool build error?

Hello, * Bruno Haible wrote on Fri, Mar 12, 2010 at 01:15:14PM CET: > 2010-03-12 Bruno Haible > > Fix problem with automake's definition of CXXLINK. > * gnulib-tool (func_create_testdir): After LT_INIT, also use LT_LANG. > Reported by Simon Josefsson and Ludovic Courtès. Is

Re: test-string-c++ test failure

Jim Meyering wrote: > In file included from test-string-c++.cc:23: > ../lib/string.h:299: error: type of 'memchr' is unknown > ../lib/string.h:299: error: invalid type in declaration before ';' token > ../lib/string.h:299: error: 'int memchr' redeclared as different kind of > symbol > /usr/include

Re: C++ libtool build error?

Ralf Wildenhues asks: > > Fix problem with automake's definition of CXXLINK. > > * gnulib-tool (func_create_testdir): After LT_INIT, also use LT_LANG. > > Reported by Simon Josefsson and Ludovic Courtès. > > Is anyone aware of a way to reproduce the bug fixed by this patch > with gnuli

Re: test-string-c++ test failure

Bruno Haible wrote: > Jim Meyering wrote: >> In file included from test-string-c++.cc:23: >> ../lib/string.h:299: error: type of 'memchr' is unknown >> ../lib/string.h:299: error: invalid type in declaration before ';' token >> ../lib/string.h:299: error: 'int memchr' redeclared as different kind o

Re: gnulib-tool: allow --libtool with --create-testdir

> 2010-03-08 Bruno Haible > > gnulib-tool: Add support for --libtool in --create-testdir. This documents it the new option: 2010-03-13 Bruno Haible * gnulib-tool (func_usage): Clarify which options are available for --create-testdir and --create-megatestdir. --- gn

Re: status of new 'c++defs' module?

Hi John, > OK, I tried updating and using the new c++defs module and hit an > error with memchr and memrchr. > ... > In file included from /usr/include/c++/4.4/cstring:46, >from /home/jwe/src/octave/liboctave/foo.cc:3: > ../libgnu/string.h:298: error: no matches converting

Re: C++ libtool build error?

Simon Josefsson wrote: > ... we need to bump the required libtool version to 2.2.x Good point, I had forgotten to do this: 2010-03-13 Bruno Haible * DEPENDENCIES (libtool): Mention libtool 2.2.x requirement in special cases. *** DEPENDENCIES.orig Sat Mar 13 16:31:08 2010 -

Re: C++ libtool build error?

Eric Blake wrote: > Which begs the question - why is gnulib-tool making C-only projects to > import C++ test files? It seems like C++ files should be excluded > unless the developer explicitly requests that both C and C++ be supported. Simon Josefsson wrote: > > So, the fix is to add an LT_LANG([

Re: C++ libtool build error?

Bruno Haible wrote: > Eric Blake wrote: ... >> Alternatively, some solution that detected that C++ code isn't relevant >> for the particular project, and didn't try to build those files. > > Actually, there are quite a number of tests that not every project may > want to carry in its testsuite, but

Re: C++ libtool build error?

Hi Jim, > Rather than lumping them all into one "-extratests" category > that is tied to the module file name, have you considered > adding new module attributes? > > Then, we could give any module one or more attributes, > and eventually exclude based on those attributes. > For example, if a pac