From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p1L9LpNi032673 for ; Mon, 21 Feb 2011 10:21:51 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As4BAIe9YU3RVditkGdsb2JhbACeJQGHfggVAQEBAQkJDAcRBCCfM4oYghyEFy+IWgEBAwWCGINBBIFoiiuISDo X-IronPort-AV: E=Sophos;i="4.62,199,1297033200"; d="scan'208";a="76280364" Received: from mail-qy0-f173.google.com ([209.85.216.173]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 21 Feb 2011 10:21:45 +0100 Received: by qyk36 with SMTP id 36so969461qyk.18 for ; Mon, 21 Feb 2011 01:21:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=agI6N7j7jeeEp3qTL6049cgt0kXd9d4JekNyfMas4DI=; b=X1y/HyzLXoAC5QABczSLoJqairOo59JjsljQjDgHnuv6Ezm9BMXCLNt0Tb5X1NBe0C O5PFTcQrQRsYuoz1RuHZzcrSlLKvbjUJkMbfWyXe25nwIylpAt/w2lKY/HzQvmxUj9Bf 33JrtobZX0CNkAZLgN1PGBsyFBifHegQ3agKw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=G9whxHX0zbSC5V7sbbeGPfKD2DhE0lNZdPPE+qsXPwY6OW2qeSvHFKZmaQDV8XMHaa e1+56ckp0JuRxIz15khHrvLPZYEDnL/IcCTGx78gu9XqXBllaQtO4lTw7lnxsZtVlkeq dz8gZG0Dh04ygtBxvFBqsCQ+j/MY6ToGfaqik= Received: by 10.229.98.198 with SMTP id r6mr772733qcn.224.1298280104130; Mon, 21 Feb 2011 01:21:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.12.137 with HTTP; Mon, 21 Feb 2011 01:21:24 -0800 (PST) In-Reply-To: References: From: Jean Krivine Date: Mon, 21 Feb 2011 10:21:24 +0100 Message-ID: To: David Allsopp Cc: "caml-list@yquem.inria.fr" Content-Type: multipart/alternative; boundary=0016364eeaca6cf85b049cc764a3 Subject: Re: [Caml-list] Compiling Windows native code --0016364eeaca6cf85b049cc764a3 Content-Type: text/plain; charset=ISO-8859-1 Sorry I wasn't being precise. The error is code independent, I tested ocamlopt on a "helloworld program". I am not using cygwin because I am trying to produce binaries which do not require cygwin to launch and I understand that there is a particular dll that is required to execute cygwin based compilation (correct?). I am using ocaml-3.11.0-win-msvc.exe that I downloaded from the web site (the gui and byte code generator work just fine). Stuff I did (probably wrongly): - install ocaml-3.11 using the installer - install MinGW Shell - MASM32 editor (for ml.exe) - flexdll (for flexlib) - and microsoft SDK (for uuid.lib) The result is a code that compiles just fine until the linking step where I get this weird error. These steps I got from an old thread (2004) here: http://groups.google.com/group/fa.caml/browse_thread/thread/fddaa68b3f497ec2 I was not able to find more recent instructions. On Sun, Feb 20, 2011 at 11:13 PM, David Allsopp wrote: > Jean Krivine wrote: > > > I am trying to produce windows native code for windows, to do so I > > have followed the instructions I found on different sources I am almost > > done but I get one last error during linking: > > Which sources? > > > ** Fatal error: cannot find file "OLDNAMES" > > > > File "caml_startup", Line 1, character 0-1 > > > > Error: Error during linking > > What command have you run to get this error? > > > I am using windows 7 and MinGW + Windows SDK 6.2 (to get uuid.lib) > > + masm32 (to have ml.exe) > > Are you compiling OCaml from sources or using a pre-packaged version (and > if so, which version of OCaml and which port). It's odd that you're > referring to Windows 7 + MinGW - if you're building for the MS toolchain, > then you should be using Cygwin but I wonder if that's just that you've > called it by the wrong name (equally, I've got a feeling that building with > MSYS now works, but I think that compiling under Cygwin is still the > "official" method). > > I haven't done an MS toolchain build of OCaml for a while, but I'm > reasonably sure that when I last used it, the Windows Server 2008 SDK > contains both the 32 and 64 bit assembler (no need to download masm > separately any more for 32 bit builds). > > > David --0016364eeaca6cf85b049cc764a3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sorry I wasn't being precise.
The error is code independent, I teste= d ocamlopt on a "helloworld program".
I am not using cygwin be= cause I am trying to produce binaries which do not require cygwin to launch= and I understand that there is a particular dll that is required to execut= e cygwin based compilation (correct?).

I am using ocaml-3.11.0-win-msvc.exe that I downloaded from the web sit= e (the gui and byte code generator work just fine).

Stuff I did (pro= bably wrongly):

- install ocaml-3.11 using the installer
- instal= l MinGW Shell
- MASM32 editor (for ml.exe)
- flexdll (for flexlib)
- and microsoft = SDK (for uuid.lib)

The result is a code that compiles just fine unti= l the linking step where I get this weird error.

These steps I got f= rom an old thread (2004) here:
http://groups.google.com/group/fa.caml/browse_thread/thread/f= ddaa68b3f497ec2

I was not able to find more recent instructions.=


On Sun, Feb 20, 2011 at 11:13 PM, David = Allsopp <dra= -news@metastack.com> wrote:
Jean Krivine wrote:

> I am trying to produce windows native code for windows, to do so I
> have followed the instructions I found on different sources I am almos= t
> done but I get one last error during linking:

Which sources?

> ** Fatal error: cannot find file "OLDNAMES"
>
> File "caml_startup", Line 1, character 0-1
>
> Error: Error during linking

What command have you run to get this error?

> I am using windows 7 and MinGW + =A0Windows SDK 6.2 (to get uuid.lib)<= br> > + masm32 (to have ml.exe)

Are you compiling OCaml from sources or using a pre-packaged version = (and if so, which version of OCaml and which port). It's odd that you&#= 39;re referring to Windows 7 + MinGW - if you're building for the MS to= olchain, then you should be using Cygwin but I wonder if that's just th= at you've called it by the wrong name (equally, I've got a feeling = that building with MSYS now works, but I think that compiling under Cygwin = is still the "official" method).

I haven't done an MS toolchain build of OCaml for a while, but I'm = reasonably sure that when I last used it, the Windows Server 2008 SDK conta= ins both the 32 and 64 bit assembler (no need to download masm separately a= ny more for 32 bit builds).


David

--0016364eeaca6cf85b049cc764a3--