libtool @2.2.6b installs sometimes lack dylibs

[gnw3]

Have 6 OSX 10.5.8 machines with essentially the same macports 1.8.2 configuration and packages. On some machines we have:

/opt/local/lib/libltdl.7.dylib

others only the static libraries. Our programs compiled on the machines with the .dylib won't run on the others.

For the machines without the dylib, libtool was installed in Nov. (so probably an older version of macports). The ones with the .dylib were installed in Jan. I did:

port uninstall -f libtool; port install libtool

on two of the machines that did not have .dylib but only one of them ended up with the .dylib! The problem appears to be that some users have symbolic links for /opt/local/bin/gfortran. If such links are present, you don't get the dylib.

I have attached the output from "port -d install libtool" from runs with (nodylib.log) and without (libtool.log) the gfortran symlinks

Note that the system that fails to install the .dylib hasL

nodylib.log:libtool.m4: error: problem compiling FC test program

[gnw3]

port -d install libtool that installs .dylib

[gnw3]

port -d install libtool that does not install .dylib

[drkp (Dan Ports)]

Is this what's causing t1lib to sometimes fail to build dylibs (see #25417, #26908)?

Do we have any idea what's causing libtool to do this?

[jmroot (Joshua Root)]

It doesn't look like this is about libtool failing to build dylibs for other software, but rather about libltdl.dylib being omitted when building libtool itself.

[drkp (Dan Ports)]

I fail at reading comprehension -- I totally missed that libltdl is part of libtool itself rather than some other random dylib.

Still wonder if it could be related, though, since the problem there appears to be that libtool is not building static libraries, and reinstalling libtool fixed it for at least one person.

[drkp (Dan Ports)]

Oh, also, per comment:ticket:25417:11, that also appears to be related to having gfortran installed.

[jmroot (Joshua Root)]

I can't reproduce this problem with libtool 2.4.

[ryandesign (Ryan Carsten Schmidt)]

Has many duplicates including #25417, #26908, #30018, #30037, #30043, #30105, #30106, #30395, #30556, and many posts on the mailing lists. I hereby consolidate all these issues into this ticket, which as far as I can tell is the earliest one.

[ryandesign (Ryan Carsten Schmidt)]

I brought the issue up with the developers of libtool on their mailing list, and ​Peter O'Gorman's reply was that this is a bug in libtool's build. libtool's build looks for a fortran compiler, and when it finds one, but it is broken, it takes note of the fact that the fortran compiler cannot build shared libraries, but this mistakenly overrides the earlier detection that the C and C++ compilers are able to (and should) create shared libraries. Peter provided a solution to prevent libtool from attempting to locate a fortran compiler, which in MacPorts we never want libtool to be doing anyway.

[ryandesign (Ryan Carsten Schmidt)]

r86790

[cooljeanius (Eric Gallager)]

Cc Me!