Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Robert Roessler <roessler@rftp.com>
To: Caml-list <caml-list@inria.fr>
Subject: Has anyone tried to build the msvc port of 3.09.1?
Date: Mon, 23 Jan 2006 21:35:06 -0800	[thread overview]
Message-ID: <43D5BC8A.7020206@rftp.com> (raw)

I can not make it build and install properly.  While I never tried 
3.09.0 (since the binary distribution was out so soon), I have 
previously built members of the 3.08 series without incident...

As suggested, I use the Cygwin shell and commands with VC7.1 (.NET 
2003) command-line tools.

Before you look too closely, things seem OK - then you realize that 
the ".opt" versions of commands are not in the bin dir.  The usual 
complement is present, including ocaml.exe, ocamlc.exe, ocamlopt.exe, 
etc... note that OCamlWin.exe insists that it cannot find ocaml.exe 
(even though the OCaml bin dir *is* on the path).  Note that ocaml.exe 
*can* be successfully started and used.

Looking at the build output for "make -f Makefile.nt install", there 
are some obvious (I believe) errors in two of the Makefiles: $(RANLIB) 
is used as a command, but since no corresponding tool exists on the 
platform (and the variable is left unassigned), this results in the 
target file "gramlib.lib" being presented *as a command* to /bin/sh... 
hacking these two by forcing RANLIB=true (to get an innocuous command 
which "succeeds") gets past these errors, but overall, the "install" 
target still does not complete.

BTW, these are the Makefiles in camlp4/lib and camlp4/ocaml_src/lib, 
in sections which include the suspicious (but not obviously related in 
this instance) comment "# Special treatment for this one...".

Ideally, either someone will point out the error of my ways (and no, 
"using Windows" is not the answer to this one), or the non-building 
status of 3.09.1 will be confirmed... with a fix forthcoming from the 
team or community.

Of course, if a binary distribution for 3.09.1 magically appeared, it 
would be nice... but it wouldn't really solve the problem. ;)

Robert Roessler
roessler@rftp.com
http://www.rftp.com


                 reply	other threads:[~2006-01-24  5:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43D5BC8A.7020206@rftp.com \
    --to=roessler@rftp.com \
    --cc=caml-list@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