* 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. Cheers, Ralf _______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
