From: "vrotaru.md@gmail.com" <vrotaru.md@gmail.com>
To: Tim Leonard <Tim@timleonard.us>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] why does "opam install graphics" fail?
Date: Wed, 14 Feb 2018 21:24:27 +0200 [thread overview]
Message-ID: <CAJgjwejbKuf3fFqaxxr5xCrmtUmeqX0QzCLowBq5s2hqK7ciZw@mail.gmail.com> (raw)
In-Reply-To: <89BCBE94-B317-45E2-BB17-B0936A9D92EC@TimLeonard.us>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
Well, since I have no experience with Macs I can only guess, but the basic
workflow is the following:
The configure.sh script tries to find the "X11/Xlib.h" file and to compile
and link a simple C program using the X headers and libs. If this fails it
assumes that X is not installed and does not build the "Graphics" module.
That's the bare-bones version, but as I said, I have no experience with
Macs:
That's what a quick search have provided me with:
https://stackoverflow.com/questions/14321038/x11-xlib-h-no-such-file-or-directory-on-mac-os-x-mountain-lion
--
Vasile Rotaru
[-- Attachment #2: Type: text/html, Size: 932 bytes --]
next prev parent reply other threads:[~2018-02-14 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F5976597-B82E-4D1A-BF50-11C3FD9BE3E1@TimLeonard.us>
2018-02-14 4:53 ` Tim Leonard
2018-02-14 6:39 ` vrotaru.md
[not found] ` <520e5733-b31b-5f65-d878-9d8de4a5f90a@bioreg.kyushu-u.ac.jp>
2018-02-14 15:03 ` Tim Leonard
2018-02-14 15:17 ` Xavier Clerc
2018-02-14 16:08 ` Tim Leonard
2018-02-14 16:15 ` Xavier Clerc
2018-02-14 17:16 ` Tim Leonard
2018-02-14 17:26 ` David Allsopp
2018-02-14 18:31 ` Tim Leonard
2018-02-14 18:36 ` vrotaru.md
2018-02-14 18:39 ` Tim Leonard
2018-02-14 19:24 ` vrotaru.md [this message]
2018-02-14 19:58 ` Tim Leonard
2018-02-14 18:37 ` Tim Leonard
[not found] ` <CAGi3GpyM_Xs2JMqpomi-SbnsGpnecfQaqXK7vJ-+kb3z4dYz3A@mail.gmail.com>
[not found] ` <CAGi3GpwZ26+mJgbuKEXqaAHd3CZgPzOcDM-keizNekT2FuAO_A@mail.gmail.com>
2018-02-14 18:28 ` Tim Leonard
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=CAJgjwejbKuf3fFqaxxr5xCrmtUmeqX0QzCLowBq5s2hqK7ciZw@mail.gmail.com \
--to=vrotaru.md@gmail.com \
--cc=Tim@timleonard.us \
--cc=caml-list@inria.fr \
/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).