From: David Allsopp <dra-news@metastack.com>
To: "matthieu.dubuget@gmail.com" <matthieu.dubuget@gmail.com>,
Caml Mailing List <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] Trying to setup mingw OCaml 3.12.1 + fresh cygwin
Date: Fri, 12 Aug 2011 12:00:36 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9C23F76F1@Remus.metastack.local> (raw)
In-Reply-To: <4E42526F.8000200@gmail.com>
Matthieu Dubuget wrote:
> From: David Allsopp <dra-news@metastack.com> wrote:
> > Good to know that 64-bit MinGW is working - that said, I thought the
> MinGW port was broken in 3.12.1 or is that not affected with the 64-bit
> compiler? Could you share details on how you configured OCaml?
>
> This is not 64 bits. i686-w64-mingw32 is 32 bits.
Ah, my bad - I mistakenly thought the mingw32 was the project and w64 the architecture!
I'm probably being low, but is the main benefit of using mingw-w64-mingw32 over the version shipped with Cygwin (-mno-cygwin) simply that the latter isn't working with 3.12.1 or is there another reason for using it?
> > #If configure is not patched, a trailing \r\n remains in camlp4's META
> > #file, which breaks it's use with ocamlfind cd
> > ${extractdir}/${findlib} && \ sed -i -e "s/camlp4 -where/camlp4 -where
> > | tr -d '\\\\015'/" configure && \ ./configure -cygpath && \ make all
> > && make opt && make install cd ${here}
I thought that one had been fixed (but clearly not, looking at my 1.2.7 META file for camlp4) - worth sending upstream to Gerd.
Going back to your original question - did those instructions work for zlib?
David
next prev parent reply other threads:[~2011-08-12 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 14:35 Matthieu Dubuget
2011-08-08 19:25 ` Adrien
2011-08-10 8:25 ` David Allsopp
2011-08-10 9:42 ` Matthieu Dubuget
2011-08-10 10:55 ` Adrien
2011-08-12 11:55 ` David Allsopp
2011-08-12 12:00 ` David Allsopp [this message]
2011-08-12 13:07 ` Adrien
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=E51C5B015DBD1348A1D85763337FB6D9C23F76F1@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=caml-list@yquem.inria.fr \
--cc=matthieu.dubuget@gmail.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