From: Martin DeMello <martindemello@gmail.com>
To: Adrien Nader <adrien@notk.org>
Cc: whitequark <whitequark@whitequark.org>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] opam-cross-windows
Date: Mon, 14 Mar 2016 14:10:56 -0700 [thread overview]
Message-ID: <CAFrFfuEnQC=JgTPB+oC5cSvGXh8nFa-6iW_S_m-AUHnG51Rx+A@mail.gmail.com> (raw)
In-Reply-To: <20160314203933.GA520@notk.org>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Yep, metapackage worked like a charm! Thanks, I think I've gotten too used
to just searching for the packages marked -dev when I run into compilation
issues.
martin
On Mon, Mar 14, 2016 at 1:39 PM, Adrien Nader <adrien@notk.org> wrote:
> On Mon, Mar 14, 2016, Martin DeMello wrote:
> > Oh, it's just a matter of installing packages one by one until things
> > compile :) More tedious than anything else; I just didn't want to go
> > through the process if someone had already. e.g. this is how I started
> off
> >
> > $ wajig install mingw-w64-x86-64-dev
> > $ wajig install mingw-w64-i686-dev
> > $ opam install ocaml-windows
> >
> > ### stderr ###
> > # + x86_64-w64-mingw32-gcc --version
> > # sh: x86_64-w64-mingw32-gcc: command not found
> >
> > I missed that there was a metapackage though; I'll give that a try.
>
> These are the packages for the headers and libraries that are required
> to get linking against Windows libraries, nothing more. In particular
> this doesn't provide a binutils nor a GCC. The metapackage should
> therefore solve your (current) issue.
>
> --
> Adrien Nader
>
[-- Attachment #2: Type: text/html, Size: 1617 bytes --]
next prev parent reply other threads:[~2016-03-14 21:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 9:02 whitequark
2016-03-14 19:55 ` Martin DeMello
2016-03-14 20:14 ` Adrien Nader
2016-03-14 20:26 ` Martin DeMello
2016-03-14 20:39 ` Adrien Nader
2016-03-14 21:10 ` Martin DeMello [this message]
2016-03-15 8:37 ` whitequark
2016-03-15 8:26 ` Soegtrop, Michael
2016-03-15 8:36 ` whitequark
2016-03-15 8:53 ` Soegtrop, Michael
2016-03-15 8:56 ` whitequark
2016-03-15 11:29 ` Soegtrop, Michael
2016-03-16 14:27 ` Andreas Hauptmann
2016-03-15 9:18 ` Adrien Nader
2016-03-15 9:12 ` David Allsopp
2016-05-20 18:38 ` Boutillier, Pierre
2016-05-20 18:45 ` whitequark
2016-05-23 8:24 ` Soegtrop, Michael
2016-05-24 6:57 ` whitequark
2016-05-24 12:35 ` Adrien Nader
2016-05-23 9:53 ` Mauricio Fernández
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='CAFrFfuEnQC=JgTPB+oC5cSvGXh8nFa-6iW_S_m-AUHnG51Rx+A@mail.gmail.com' \
--to=martindemello@gmail.com \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=whitequark@whitequark.org \
/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 NNTP newsgroup(s).