search

casseopea2 / gperftools

Automatically exported from code.google.com/p/gperftools
BSD 3-Clause "New" or "Revised" License
1 stars 0 forks source link

Extraneous Check #144

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ./configure
2. checking whether we are using the GNU Fortran 77 compiler... no
3.

What is the expected output? What do you see instead?
This check shouldnt be there. Is there any code which is in fotran

What version of the product are you using? On what operating system?
1.3

Please provide any additional information below.

Original issue reported on code.google.com by bornlibr...@gmail.com on 13 Jun 2009 at 12:51

GoogleCodeExporter commented 9 years ago 
This wouldnt be an issue but on my system where we dont have pipe files every 
bit  
of data is actually written to the disk. So what takes senconds on linux takes 
minutes here. Just to examplify building GNU Tools package takes more than 20 
hours 
on my system.

Original comment by bornlibr...@gmail.com on 13 Jun 2009 at 3:25

GoogleCodeExporter commented 9 years ago 
Unfortunately this is not under my control: this check is done deep in the 
libtool
library.  We definitely need libtool to make the libraries.  I spent some time a
while ago trying to figure out how to disable the fortran check, and couldn't 
figure
out a way to do it.

I feel for you that the configure check takes so long, but I don't see any way 
around
it.  My best suggestion is to run ./configure -C, so at least it will cache 
results
for next time.

Original comment by csilv...@gmail.com on 14 Jun 2009 at 4:39