[Top][All Lists]

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

Re: C++ libtool build error?

From: Simon Josefsson
Subject: Re: C++ libtool build error?
Date: Wed, 17 Mar 2010 12:22:17 +0100
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)

Bruno Haible <address@hidden> writes:

> Actually, there are quite a number of tests that not every project may
> want to carry in its testsuite, but that should be packageable via
> --create-testdir:
>   - The C++ tests of the modules 'string', 'stdlib', etc.
>   - The tests that ask for the superuser password ('idpriv-drop',
>     'idpriv-droptemp').
>   - The long-running tests of the 'havelib' module (currently still in
>     gettext).

I agree, having a mechanism to handle this would be useful.

> Additionally, the user who installs a package might want to disable the C++
> part even if it is packaged as part of the tarball. I'm applying this.

Thanks, but the original problem is still not addressed -- building
libidn (and libunistring, and likely other projects too) fails after the
C++ self-tests were introduced in gnulib.  What is the supported
solution for that problem?


reply via email to

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