diff options
| author | allen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac> | 2003-12-31 03:14:25 +0000 |
|---|---|---|
| committer | allen <allen@17b73243-c579-4c4c-a9d2-2d5706c11dac> | 2003-12-31 03:14:25 +0000 |
| commit | bf433e638527ac20d99df466fe00bbfa2d7ffde9 (patch) | |
| tree | 3ca7058bfc8d422796b281f6cbb9ac70c54e594b /doc/FAQ | |
| parent | 687f120853f38d6e7af80a5d4ffa91067f09b643 (diff) | |
Added the missing answer for question C31 (which is now C37)
git-svn-id: http://svn.cactuscode.org/flesh/trunk@3482 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 16 |
1 files changed, 13 insertions, 3 deletions
@@ -1,7 +1,7 @@ Cactus Code Frequently Asked Questions -$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.74 2003-12-23 06:01:09 allen Exp $ +$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.75 2003-12-31 03:14:25 allen Exp $ Also available at http://www.cactuscode.org/Documentation/FAQ @@ -140,8 +140,6 @@ C29 On linking I get an "unresolved text symbol" for a scheduled function C30 (Linux) Using the Intel Fortran compiler I get the error "/usr/bin/ld cannot find -lintrins" on linking. -C31 Why can't I use different F90 and F77 compilers with Cactus? - C31 I just want to check that one thorn compiles correctly, can I test this without compiling all the thorns which come before it? @@ -162,6 +160,8 @@ C35 I started building a Cactus configuration and it asked me if C36 (Linux) Compiling Cactus with Redhat 8 or 9 it fails in CactusBase/IOUtil because the system failed to find <sys/stat.h> +C37 Why can't I use different F90 and F77 compilers with Cactus? + ------------------------------------------------------------------------------ Running: @@ -1071,6 +1071,16 @@ C36 (Linux) Compiling Cactus with Redhat 8 or 9 with Intel compilers my build available here. */ # ifndef __dev_t_defined +C37 Why can't I use different F90 and F77 compilers with Cactus? + + Because Cactus does some automatic name mangling to allow you to call + Fortran routines from C and vice-versa, and different compilers will use + different conventions for the way that they generate routine names in + the object files. This means that you would only be able to use different + compilers for F90 and F77 if they used the same conventions. In + principle we could check to make sure that they are compatible, but for + now we require you to use the same compiler for both F77 and F90 code. + ------------------------------------------------------------------------------ Running: |