On Thu, 2004-01-29 at 01:35, Daniel Reed wrote: > On 2004-01-28T15:59-0000, Scott James Remnant wrote: > ) On Wed, 2004-01-28 at 15:15, Daniel Reed wrote: > ) > Since there does not appear to be any C++ code (.cc, .cxx, .C) in libtool, > ) > would it be possible for the next release of libtool to not: > ) There isn't any C code either ... it checks for various compilers so it > ) can provide support for them (ie. you can go "libtool g++"). > > The problem I was reporting is not so much the testing for C++ as it was the > failing of ./configure if a C++ preprocessor was not available. There is C > code in the various examples directories, so failing for lack of a C > compiler might at least be reasonable. > That's actually an Autoconf macro that's failing, unfortunately. It's an irritant, but I've not figured out a way of getting around it short of overriding AC_MSG_ERROR.
Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
