| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
A Fortran file is compiled to an object file, which is then searched
for certain patterns. The detection can now handle multiple matches
per "line", which is necessary for gcc 4.3.
git-svn-id: http://svn.cactuscode.org/flesh/trunk@4463 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
| |
git-svn-id: http://svn.cactuscode.org/flesh/trunk@3495 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Cactus/789
git-svn-id: http://svn.cactuscode.org/flesh/trunk@2380 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
| |
sometime in the last few commits.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@2185 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hopefully configuring with and without the different fortran compilers
now works. You can (hopefully) say
F90=none
and/or
F77=none
and get no complaints about unknown compilers and get all the underscores sorted out.
In doing this I removed for now the F90_NOT_SET that I had put in before
so that you get a semi decent line if you try and compile a fortran file
with no fortran compiler since it was stretching my logic capabilities. Now
you will get a less decent line, but it will still say "none" for the
compiler rather than saying nothing. I'll try and remember to put it
back.
I'm think we can easily add the ability to have different F77 and F90
compilers as well, so long as they have the same underscore behaviour,
but probably noone needs that.
git-svn-id: http://svn.cactuscode.org/flesh/trunk@2074 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
| |
if no compilers are found. This fix stops the perl script trying to compile
a test program to look for C-Fortran name translation if there is no compiler.
git-svn-id: http://svn.cactuscode.org/flesh/trunk@1988 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@1842 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
|
| |
it work with the SGI ia64 compiler, and should also make
it work on the SX 5.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@1662 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
| |
no fortran whatsoever.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@1459 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@1393 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@601 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
| |
a .o file.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@579 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@351 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
|
|
|
| |
_C in front of common block names in the symbol table.
You'll need to regenerate your fortran_name.pl files after updating with
these changes.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@350 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
use
make <config> options=<option-file-name>
when making a new configuration.
<option-file-name> has the format of
keyword value
or keyword = value
Note that even though it will allow a vlue to be blank, the configure
script itself will ignore this, so it's not so easy to tell it to ignore,
say, your f90 compiler.
The configure script now uses the f90 compiler for f77, or the f77
compiler if there is no f90 compiler.
The configure.pl script will produce a dummy fortran_name perl script if
there is no fortran compiler.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@319 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@303 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
| |
git-svn-id: http://svn.cactuscode.org/flesh/trunk@298 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
distinct.
Since at the moment all machines seem to have the same name translation for
common block names as for subroutine names, I've disabled the common block
test, and hence the FORTRAN_COMMON_NAME macro, for the moment. Just use
FORTRAN_NAME.
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@115 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@113 17b73243-c579-4c4c-a9d2-2d5706c11dac
|
|
configure and config.h.in are generated by running autoconf and autoheader
respectively.
The resulting configure file can then be run to produce
make.config.defn
config.h
fortran_name.pl
You must set an environment variable with the name of the executable first.
It should be run from the config-data directory of a configuration - e.g
setenv EXE cctk
$(CCTK_HOME)/lib/make/configure
Tom
git-svn-id: http://svn.cactuscode.org/flesh/trunk@61 17b73243-c579-4c4c-a9d2-2d5706c11dac
|