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

[Paul Laight]

Thanks for the feedback.

All the best with the project.

Regards,

Paul Laight


www.quantxautomation.com
address@hidden
+44(0)20 7692 1724

4th Floor | 100 New Bond Street | Mayfair | London | ENGLAND | W1S 1SP

QuantX Automation Ltd, registered office:  145-157 St. John Street, London, EC1V 4PY.  Registered number: 07091029
This E-mail transmission may contain confidential or legally privileged information that is intended for the addressee only. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or reliance upon the contents of this E-mail is strictly prohibited.  Please note that e-mail may be susceptible to data corruption, interception and unauthorised amendment. QuantX Automation Ltd does not accept any liability for any such corruption, interception, amendment or the consequences thereof.
Please consider the environment - only print this email if necessary

On 28 Aug 2010, at 19:42, Ralf Wildenhues wrote:

Hello Paul,

* Paul Laight wrote on Mon, Aug 23, 2010 at 01:27:07PM CEST:

The make check generated the attached

Please advise.

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:

./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.

You can still use this Libtool otherwise.

Cheers,
Ralf