[Top][All Lists]

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

Re: [bug-libunistring] Re: C++ libtool build error?

From: Simon Josefsson
Subject: Re: [bug-libunistring] Re: C++ libtool build error?
Date: Fri, 12 Mar 2010 13:46:01 +0100
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)

Bruno Haible <address@hidden> writes:

> So, the fix is to add an LT_LANG([CXX]) invocation to your configure.ac.
> This fixes it for libunistring.

That doesn't make a lot of sense to me because

   1) It violates the modularity of gnulib.  Gnulib is adding the C++
      code to my project, so I believe gnulib should be responsible for
      making sure the files build.

   2) LT_LANG([CXX]) doesn't exist in libtool 1.5.x which is still
      supported by gnulib.

The fix you applied is just for --create-testdir (right?) so that patch
by itself doesn't modify anything for libidn or libunistring as far as I
can tell.

If we really want to force projects that use gnulib to carry out the
required steps, we need to bump the required libtool version to 2.2.x
and document that users needs to add LT_LANG([CXX]) to their
configure.ac [when they use any of the modules that pull in C++ code].

However, I would prefer any other solution that made the C++ code added
by gnulib actually build and that we continue to support libtool 1.5.x.
Several still supported platforms doesn't have libtool 2.x, notably
Ubuntu 8.04 LTS.

Alternatively, some solution that detected that C++ code isn't relevant
for the particular project, and didn't try to build those files.



reply via email to

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