From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Adrien Nader <adrien@notk.org>
Cc: Thomas Gazagnaire <thomas@ocamlpro.com>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] lablgtk2: cannot find the Pango module?
Date: Wed, 17 Jul 2013 15:26:40 +0200 [thread overview]
Message-ID: <m2a9ll5ncf.fsf@polytechnique.org> (raw)
In-Reply-To: <20130716192129.GA8915@notk.org>
adrien@notk.org writes:
> Hi,
>
> On Tue, Jul 16, 2013, Thomas Gazagnaire wrote:
>> > ocamlopt -g -I lwt -I ubase -I system -I fsmonitor -I fsmonitor/linux -I fsmonitor/windows -I system/generic -I lwt/generic -ccopt -mmacosx-version-min=10.5 -I +lablgtk2 -c /Users/schmitta/src/unison/trunk/src/uigtk2.ml
>> > File "/Users/schmitta/src/unison/trunk/src/uigtk2.ml", line 81, characters 26-48:
>> > Error: Unbound module Pango
>> >
>> > The strange thing is that when I launch the lablgtk2 toplevel, I can do
>> > a "open Pango" with no error.
>>
>> I guess the -I +lablgtk2 does not use the right path. Under OPAM, files are installed in `opam config var lib`/labgtk (`opam config var labgtk:lib` in master). Or you can use the ocamlfind installation path: `ocamlfind query lablgtk`.
>
> I know nothing about mac os x, opam and unison but nowadays lablgtk uses
> ocamlfind. Maybe unison needs to be updated.
>
> Lablgtk without ocamlfind might work but I'd say that if it breaks, you
> get to keep the pieces.
> (plus, I'm a member of the AANUOO: Association Against Non-Usage Of
> Ocamlfind :-) )
Thank you Thomas and Adrien, using ocamlfind made things work. I'll see
what is the best way to propagate these building changes upstream.
Alan
prev parent reply other threads:[~2013-07-17 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 13:38 Alan Schmitt
2013-07-16 7:37 ` Thomas Gazagnaire
2013-07-16 19:21 ` Adrien Nader
2013-07-17 13:26 ` Alan Schmitt [this message]
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=m2a9ll5ncf.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=thomas@ocamlpro.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