[Top][All Lists]

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

Re: [libtool 2.2] testsuite: 19 35 36 44 45 46 48 49 50 51 52 53 60 61 6

From: Ralf Wildenhues
Subject: Re: [libtool 2.2] testsuite: 19 35 36 44 45 46 48 49 50 51 52 53 60 61 62 64 failed [GNU/Linux PowerPC]
Date: Thu, 6 Mar 2008 20:50:32 +0100
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

* Bob Friesenhahn wrote on Thu, Mar 06, 2008 at 08:43:15PM CET:
> On Thu, 6 Mar 2008, Peter O'Gorman wrote:
>> I think the test for a working GCJ should be in libtool, and unset GCJ,
>> avoid adding the tag etc.if it is found to be nonfunctional. We would
>> have to issue a warning during configure or something. Does not look to
>> be quite as easy as this patch though, if you want to apply this one as
>> a stop-gap measure, that is fine.

I'm considering doing that (the stop-gap measure).

> If libtool is integrated into a package and the package declares that it 
> needs a Java compiler, then failure to pass basic tests should cause 
> configure to quit with an error (similar to the way configure fails if 
> the C compiler does not work).

But that should not be Libtool's decision, but the package's.

> If libtool is built stand-alone (as in 
> our distribution) then there should be a warning but the user should 
> still be able to build and install libtool.

Yes, and I can conceive just as well a libtool-using package which may
optionally use a Java compiler, and thus its configure script should not
bail out at Libtool's whim either.


reply via email to

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