From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: new version of ocaml package (4.01.0-1)
Date: Mon, 28 Oct 2013 20:17:00 -0000 [thread overview]
Message-ID: <526EC657.4050401@users.sourceforge.net> (raw)
In-Reply-To: <AE032C4F-E944-4F4C-A496-71270FC2128E@inria.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.
Yaakov
next prev parent reply other threads:[~2013-10-28 20:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 17:23 RFU: ocaml-3.12.1-1 Damien Doligez
2011-12-15 19:21 ` Corinna Vinschen
2011-12-15 19:26 ` Corinna Vinschen
2011-12-15 22:24 ` Damien Doligez
2011-12-16 10:01 ` Corinna Vinschen
2011-12-19 16:05 ` Corinna Vinschen
2011-12-20 22:21 ` Damien Doligez
2011-12-21 3:21 ` Yaakov (Cygwin/X)
2011-12-21 10:38 ` Damien Doligez
2011-12-21 15:26 ` RFU: ocaml-3.12.1-2 Damien Doligez
2011-12-21 15:50 ` Corinna Vinschen
2013-06-07 12:31 ` [RFU] ocaml-4.00.1-1 Damien Doligez
2013-06-07 14:19 ` Corinna Vinschen
2013-06-09 14:42 ` Damien Doligez
2013-06-10 8:27 ` Corinna Vinschen
2013-06-11 15:37 ` Damien Doligez
2013-06-13 18:31 ` Yaakov (Cygwin/X)
2013-06-14 0:42 ` Florent Monnier
2013-06-18 23:09 ` Yaakov (Cygwin/X)
2013-06-07 18:01 ` Yaakov (Cygwin/X)
2013-10-25 9:25 ` new version of ocaml package (4.01.0-1) Damien Doligez
2013-10-25 17:39 ` Yaakov (Cygwin/X)
2013-10-28 20:17 ` Yaakov (Cygwin/X) [this message]
2013-10-29 9:14 ` Corinna Vinschen
2013-10-29 17:30 ` Yaakov (Cygwin/X)
2013-10-29 17:54 ` Corinna Vinschen
2013-10-31 2:13 ` Yaakov (Cygwin/X)
2013-11-01 10:28 ` Damien Doligez
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=526EC657.4050401@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).