From: SP <sp@orbitalfox.eu>
To: Robert Muller <robert.muller2@gmail.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] A question RE labltk installation on MacOS Sierra
Date: Sun, 21 Jan 2018 23:06:11 +0000 [thread overview]
Message-ID: <20180121230611.0152ef9c@darkstar> (raw)
In-Reply-To: <CAKmYinmA16XhY5i0_1q_kj6jJ7nX+ESLxmmjWZNF_6brq4PyRQ@mail.gmail.com>
On Sun, 21 Jan 2018 14:15:28 -0500
Robert Muller <robert.muller2@gmail.com> wrote:
> Hello, I know this isn't the right forum for questions like the
> following. Can someone refer me to the right forum?
This also exists: https://discuss.ocaml.org
I don't see anything wrong with asking this here, although it's very
niche.
> but it doesn't symlink it in /usr/local/. I'm having trouble
> convincing the Makefile for labltk to find the .h files in
> /usr/local/opt/tcl-tk/include/
Did you try `brew link tcl-tk`?
I found that is a manual step for some packages.
--
SP
next prev parent reply other threads:[~2018-01-21 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 19:15 Robert Muller
2018-01-21 23:06 ` SP [this message]
2018-01-22 9:08 ` Jacques Garrigue
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=20180121230611.0152ef9c@darkstar \
--to=sp@orbitalfox.eu \
--cc=caml-list@inria.fr \
--cc=robert.muller2@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