caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Philip A. Viton" <viton.1@osu.edu>
To: caml-list@yquem.inria.fr
Subject: ocamlopt under win32
Date: Fri, 06 Oct 2006 11:11:07 -0400	[thread overview]
Message-ID: <7.0.1.0.2.20061006104319.022cbd88@osu.edu> (raw)


Can anyone tell me what's going wrong here?

Computer: running win xp/sp2 on amd 64
ocamlopt: 3.09.0
ms files: from visual studio 6

I try the following (the smallest independent part of the Hevea distribution):

==== non verbose =====


C:\ProgramFiles\OCaml\hevea\hevea-1.09\native> 
c:\ProgramFiles\ocaml\bin\ocamlopt  -c bibhva.ml


C:\ProgramFiles\OCaml\hevea\hevea-1.09\native> 
c:\ProgramFiles\ocaml\bin\ocamlopt  -o bibhva.exe bibhva.cmx

libasmrun.lib(compact.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(ints.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(floats.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(major_gc.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(gc_ctrl.obj) : error LNK2001: unresolved external symbol __ftol2
bibhva.exe : fatal error LNK1120: 1 unresolved externals
Error during linking


===================== verbose


C:\ProgramFiles\OCaml\hevea\hevea-1.09\native>c:\ProgramFiles\ocaml\bin\ocamlopt
   -verbose -c bibhva.ml
+ ml /nologo /coff /Cp /c /Fo"bibhva.obj" "c:\temp\camlasmfaa835.asm">NUL

C:\ProgramFiles\OCaml\hevea\hevea-1.09\native>c:\ProgramFiles\ocaml\bin\ocamlopt
   -verbose -o bibhva.exe bibhva.cmx
+ ml /nologo /coff /Cp /c /Fo"c:\temp\camlstartupca51b3.obj" 
"c:\temp\camlstartu
p7461f9.asm">NUL
+ cl /nologo /MT /Fe"bibhva.exe" -I"C:\ProgramFiles\OCaml\lib" 
"c:\temp\camlstar
tupca51b3.obj" "C:\ProgramFiles\OCaml\lib\std_exit.obj" "bibhva.obj" 
"C:\Program
Files\OCaml\lib\stdlib.lib" 
"C:\ProgramFiles\OCaml\lib\libasmrun.lib" advapi32.
lib
libasmrun.lib(compact.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(ints.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(floats.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(major_gc.obj) : error LNK2001: unresolved external symbol __ftol2
libasmrun.lib(gc_ctrl.obj) : error LNK2001: unresolved external symbol __ftol2
bibhva.exe : fatal error LNK1120: 1 unresolved externals
Error during linking



This link failure (with the same unresolved externals message) 
appears for all other parts of the hevea distribution too, so it 
seems that something is going wrong with any attempt to link.



There's an earlier message on the list to the effect that VC6 isn't 
usable with the most recent ocaml distribution: is this really true?

There's also a remark in the most recent ocaml bugfix release to the 
effect that something is being fixed specifically for the AMD chip : 
could that be the problem?


Any help very gratefully received!



------------------------
Philip A. Viton
City Planning, Ohio State University
275 West Woodruff Avenue, Columbus OH 43210
viton.1@osu.edu


             reply	other threads:[~2006-10-06 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 15:11 Philip A. Viton [this message]
2006-10-09 16:32 ` [Caml-list] " Xavier Leroy
2006-10-10  9:41   `  Dr. Axel Poigné 

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7.0.1.0.2.20061006104319.022cbd88@osu.edu \
    --to=viton.1@osu.edu \
    --cc=caml-list@yquem.inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).