bug#8635: Some Fortran files don't have the extensions automake wants

2011-05-08 Thread Peter Williams
I'm working on wrapping a large, preexisting piece of Fortran code with
an Autotools-based build system. The code is written in Fortran 90 and
uses .for for the file extension. Unfortunately, automake thinks that
.for files are Fortran 77 code, so the wrong compiler gets used and
chokes on the F90 constructs.

It's not practical for me to rename the files -- tracking upstream would
become impossible. Would it be possible to provide a way for me to tell
automake that my .for files are actually Fortran 90, not Fortran 77? As
far as I can tell, this mapping is simply hardcoded
in /usr/bin/automake. It wouldn't be the most pleasant, but it'd suffice
if there were some global variable that I could set that would say hey,
Automake, .for files are F90. One could imagine more generic solutions
as well, but Fortran is probably the only language that has these kinds
of problems.

Thanks,

Peter

-- 
Peter Williams / pwilli...@astro.berkeley.edu
Department of Astronomy, UC Berkeley






Re: Automake mingw cross compile problems

2011-05-08 Thread Erik de Castro Lopo
Erik de Castro Lopo wrote:

 The problem is that the test programs don't get built. Or rather
 something gets built and put in the G72x/.libs directory, but there
 is nothing in the G72x/ directory for the generated Makefile to run.

Just as an addendum to this bug report, the G72x/.libs/ directory
also contains a file named g72x_test_ltshwrapper. This file is a
bash script, but is not executable.

However, running it as:

   bash G72x/.libs/g72x_test_ltshwrapper

results in the error:

G72x/.libs/g72x_test_ltshwrapper: error:
 `/home/erik/test/src/G72x/.libs/.libs/g72x_test.exe' does not exist

suggesting that the script was actually meant for one directory
above where it ended up.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/