This is the mail archive of the
mailing list for the Cygwin project.
Re: new version of ocaml package (4.01.0-1)
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 28 Oct 2013 15:17:27 -0500
- Subject: Re: new version of ocaml package (4.01.0-1)
- Authentication-results: sourceware.org; auth=none
- References: <03567512-0765-4AA9-9316-92AA3D5D71EE at inria dot fr> <8DC287A3-12E5-4AF7-AFFB-647396555DB0 at inria dot fr> <51B21FD1 dot 1070100 at users dot sourceforge dot net> <AE032C4F-E944-4F4C-A496-71270FC2128E at inria dot fr>
On 2013-10-25 04:25, Damien Doligez wrote:
So, here it is: I have a new version of the OCaml package (4.01.0-1),
both for 32 and 64 bits. I have uploaded the files to cygwin.com,
but I haven't put the !ready files yet.
Both packages are marked as "test":
- For 32 bits, because I don't want to hurt you again. I'm guessing
that a "test" version of the package will let you recompile the
libraries in Ports, and then when you tell me you're ready, I'll make
a "curr" version.
Ack, I'll let you know when I'm finished the rebuild (but see below).
- For 64 bits, because we don't have Flexdll yet, so dynlink is not
supported, which means that many OCaml programs won't work. I've
already prodded the Flexdll upstream. I'm publishing this because
it's the best we can have on 64-bit for the moment.
I started working on porting flexdll-0.31, but the testsuite is failing
with "cannot relocate, target is too far" errors; IIUC the issue has to
do with our use of the medium code model. In the meantime, the primary
use of OCaml on supported platforms is native code compilation, so I
suggest we make this stable on x86_64.
Both packages include labltk.
Are you sure? AFAICS it's only in the x86_64 package.
Because of the extra dependencies, for the next release, I suggest
making a separate ocaml-labltk package with usr/bin/labltk and
usr/lib/ocaml/labltk/ (and usr/lib/ocaml/stublibs/dlllabltk.so on x86),
along with adding --exclude=*labltk* to ocaml_base_CONTENTS. We do a
similar thing with Python and Ruby's Tcl/Tk support.