|
From: | Peter O'Gorman |
Subject: | bug#9795: Disabling fortran (what's it for?) |
Date: | Fri, 21 Oct 2011 11:35:09 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.22) Gecko/20110906 Fedora/3.1.14-1.fc14 Thunderbird/3.1.14 |
On 10/20/2011 07:47 PM, Peter O'Gorman wrote:
I think that because the installed fortran compiler is somehow broken libtool detects that the compiler can not create shared libraries. Fortran being tested last must overwrite the varaibles that were set for the C and C++ compiler - so libtool does not create any shared libraries at all. I'll look into it.
The "can_build_shared" shell variable is not tagged (not one var per compiler), so even though the C and C++ compilers would work, any broken compiler that comes later in the tests will cause libtool to not build shared libraries.
The code in question is a bit of a mess and may take a little sorting out. In the meantime, if you build libtool with configure F77=no FC=no; makethen it should disable the fortran tag. The installed libtool script then will not be able to build fortran code, but the use of the installed build script to build packages is not encouraged anyway.
Your users with broken fortran compilers will continue to see brokenness building other packages, since most autotools based build systems embed some version of libtool.
Peter
[Prev in Thread] | Current Thread | [Next in Thread] |