[Top][All Lists]

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

Re: [libtool 2.2.10] testsuite: 28 29 102 failed

From: Ralf Wildenhues
Subject: Re: [libtool 2.2.10] testsuite: 28 29 102 failed
Date: Wed, 13 Oct 2010 20:35:52 +0200
User-agent: Mutt/1.5.20 (2010-08-04)

Hello again Paul,

A while ago you reported a Libtool testsuite failure:

* Ralf Wildenhues wrote on Sat, Aug 28, 2010 at 08:42:50PM CEST:
> Thanks for the report.  The failures are fairly benign, the only real
> issue being that the GNU Fortran compiler version on your system doesn't
> like being handed convenience archives but no plain objects on the
> command line:
> * Paul Laight wrote on Mon, Aug 23, 2010 at 01:27:07PM CEST:
> > ./convenience.at:151: $LIBTOOL --tag=F77 --mode=link $F77 $FFLAGS $LDFLAGS 
> > -o liba12.la liba1.la liba2.la -rpath /notexist
> > stderr:
> > i686-apple-darwin8-gfortran-4.2: no input files; unwilling to write output 
> > files
> > stdout:
> > libtool: link: gfortran -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o 
> > .libs/liba12.0.dylib   -Wl,-force_load,./.libs/liba1.a 
> > -Wl,-force_load,./.libs/liba2.a     -install_name  /notexist/liba12.0.dylib 
> > -compatibility_version 1 -current_version 1.0 -Wl,-single_module
> > ./convenience.at:151: exit code was 1, expected 0
> > 28. convenience.at:109: 28. F77 convenience archives (convenience.at:109): 
> > FAILED (convenience.at:151)
> We should probably work around this, but it is only a minor issue.

And I forgot that we already have measures in place to support this:
the tag variable compiler_needs_object.  Which gfortran version is this,
what does
  gfortran --version

print?  Maybe we can set it to yes based on the version string, or we
need a test (but that would be ugly).

Can you do me a favor and build this Libtool package again, then after
'make all', edit the toplevel generated libtool script:
- search for "BEGIN LIBTOOL TAG CONFIG: F77"
- below that, search for "compiler_needs_object="
- set that to yes

do the same a couple hundred lines below again, with the tag config for

Then rerun the failed tests, like this:
  make check-local TESTSUITEFLAGS='28 29 102'


reply via email to

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