[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9795: Disabling fortran (what's it for?)
From: |
Ralf Wildenhues |
Subject: |
bug#9795: Disabling fortran (what's it for?) |
Date: |
Wed, 19 Oct 2011 21:17:05 +0200 |
Hello Ryan,
* Ryan Schmidt wrote on Wed, Oct 19, 2011 at 08:24:41AM CEST:
> Hello, I'm writing on behalf of the MacPorts project. In MacPorts, many users
> (some of the tickets are listed below) have experienced a problem building
> libtool, where the shared library libltdl.dylib doesn't get built. It took
> awhile to identify that this was the problem, because the failure was silent;
> the libtool port seemed to install successfully, but did not contain
> libltdl.dylib, which caused various problems for other software down the
> road. Once we added a check to the libtool port to prevent the installation
> from completing if libltdl.dylib didn't get built, we were able to work out
> that the common thread was the presence of a fortran compiler. Some users had
> a fortran compiler installed at /usr/bin/gfortran; others had /usr/bin/g77 or
> /bin/f77. While we find it an error for any 3rd-party package to have
> installed files in those locations, since those are system directories, we
> nevertheless have the situation that these packages do exist, so we have to
> deal with them.
This is libtool < 2.0, right?
Please update. We've fixed this years ago.
Thanks,
Ralf