CCL: RE : Compilation troubles
- From: BOUYER Frédéric 153746
<FB153746/./ATIL.CEA.FR>
- Subject: CCL: RE : Compilation troubles
- Date: Mon, 17 Oct 2005 09:16:50 +0200
Sent to CCL by: =?iso-8859-1?Q?BOUYER_Fr=E9d=E9ric_153746?=
[FB153746..ATIL.CEA.FR]
Dear All, and Dear Perry,
Here, you will find the errors returned by ifort, the intel fortran compiler
(v. 8.0). It was linked with the MKL libraries. This is only at the end that
these errors were produced ... 80 .exe were build instead ... See below ....
Between == ==
Changing the compiler, ifort by g77, the errors are not the same :
___________________ with g77 ___________________________________________
chkmove.f: In subroutine `ckcon':
chkmove.f:419:
Subroutine ChkWRI(DoWrt,IFormU,IA,Len)
1
chkmove.f:761: (continued):
Call ChkWRI(ToFmt,IFormU,V(INBond),NAtoms)
2
Argument #3 of `chkwri' is one type at (2) but is some other type at (1)
[info -f g77 M GLOBALS]
chkmove.f:419:
Subroutine ChkWRI(DoWrt,IFormU,IA,Len)
1
chkmove.f:762: (continued):
Call ChkWRI(ToFmt,IFormU,V(IIBond),NAtoms*MxBond)
2
Argument #3 of `chkwri' is one type at (2) but is some other type at (1)
[info -f g77 M GLOBALS]
make: *** [chkmove.o] Error 1
____________________________________________________________________________
________
Well, is there only a global variable to change in order to run g77, or is
it more complicated ?
Or, how to overcome the errors made by ifort ? I am looking forward to
reading from you and any tips that could help me.
Regards,
Frédéric
====================== BEGIN OF MADNESS AND INSANE TALK
(ifort)=============================
newzmat.a(newzmt.o)(.text+0xa3d): In function `newzmt_':
: r: référence indéfinie vers « roundz_ :
référence indéfinie vers « roundz_
»
newzmat.a(newzmt.o)(.text+0xef6): In function `newzmt_':
: référence indéfinie vers « symavg_ référence
indéfinie vers « symavg_ »
newzmat.a(newzmt.o)(.text+0x28ba): In function `newzmt_':
: référence indéfinie vers « wcache_ »
newzmat.a(newzmt.o)(.text+0x3775): In function `newzmt_':
: référence indéfinie vers « wxyz_ »
newzmat.a(newzmt.o)(.text+0x37d8): In function `newzmt_':
: référence indéfinie vers « wpcmod_ »
newzmat.a(newzmt.o)(.text+0x382e): In function `newzmt_':
: référence indéfinie vers « wfrag_ »
newzmat.a(newzmt.o)(.text+0x3884): In function `newzmt_':
: référence indéfinie vers « wmodel_ »
newzmat.a(newzmt.o)(.text+0x39a4): In function `newzmt_':
: référence indéfinie vers « wppp_ »
newzmat.a(newzmt.o)(.text+0x39f0): In function `newzmt_':
: référence indéfinie vers « wzindo_ »
newzmat.a(newzmt.o)(.text+0x3a39): In function `newzmt_':
: référence indéfinie vers « wcon_ »
newzmat.a(newzmt.o)(.text+0x3a9c): In function `newzmt_':
: référence indéfinie vers « wmcmod_ »
newzmat.a(newzmt.o)(.text+0x3b12): In function `newzmt_':
: référence indéfinie vers « wmopac_ »
newzmat.a(newzmt.o)(.text+0x4a1e): In function `newzmt_':
: référence indéfinie vers « rdxyz_ »
newzmat.a(newzmt.o)(.text+0x5a2e): In function `newzmt_':
: référence indéfinie vers « rdpcmz_ »
newzmat.a(newzmt.o)(.text+0x5e5c): In function `newzmt_':
: référence indéfinie vers « rmopac_ »
newzmat.a(rdmm2z.o)(.text+0x6a): In function `rdmm2z_':
: référence indéfinie vers « readmm_ »
newzmat.a(bondtb.o)(.text+0xf8): In function `bondtb_':
: référence indéfinie vers « unpka_ »
newzmat.a(bondtb.o)(.text+0x130): In function `bondtb_':
: référence indéfinie vers « unpkb_ »
============================================================================
==================
-----Message d'origine-----
De : owner-chemistry=ccl.net [mailto:owner-chemistry=ccl.net]
Envoyé : jeudi 13 octobre 2005 00:02
À : B, F
Objet : CCL: Compilation troubles
Sent to CCL by: "Perry E. Metzger" [perry++piermont.com]
> Did anyone compile gaussian03 with g77 ? I have only the first
> executable, but all the .exe are not build, because of some undefined
> references. I try to compile the source code on a PC Xeon with redhat
> 9. Many thanks in advance for any kind of hep and any tip that could
> help me (makefile and flags to share).
Hi!
In general, undefined references are caused by a failure in the link command
line to refer to all needed pieces of software, but without the actual error
information it is difficult to answer in your specific case.
In order to make it easier to help with answering questions like this, it is
helpful if you post a transcript (or an edited transcript) of the compile,
and if you give us information on the versions of the software you are
trying to use.
To produce an accurate transcript, I suggest you either redirect both stdout
and stderr to a file, like this:
make >make.out 2>&1
This will produce a full transcript of the compile, called "make.out"
(You
can learn more about redirection commands in the man page for the standard
linux shell, via "man bash"). BTW, that works for any command, not
just
"make".
Alternatively, you can use the "script" command ("man
script" for details).
"script" is especially helpful if you are posting about problems with
an
interactive command.
Versions of all the things you are using can, as I said, be helpful. Most of
the gcc based compile tools on Linux will tell you their version numbers if
you ask like this:
g77 --version
or
gcc --version
The version of the software you are compiling is also often quite important,
as well as how you set it up to compile.
By the way, on linux, you don't generally think of it as a ".EXE" file
since
linux does not use the Microsoft .EXE convention. It is better to call your
.o files "object files" or ".o files", and your final liked
executable
simply "the executable".
Perryhttp://www.ccl.net/cgi-bin/ccl/send_ccl_messagehttp-:-//www.ccl.net/chemistry/sub_unsub.shtmlhttp-:-//www.ccl.net/spammers.txt