From: Basile Starynkevitch <basile@starynkevitch.net>
To: Nicolas Ojeda Bar <nojb@math.harvard.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] native dynlink
Date: Sat, 5 Feb 2011 20:21:52 +0100 [thread overview]
Message-ID: <20110205202152.6dd14cbf.basile@starynkevitch.net> (raw)
In-Reply-To: <BC721858-4D0D-4ACF-9560-7B5238DCE6A0@math.harvard.edu>
On Sat, 5 Feb 2011 14:03:21 -0500
Nicolas Ojeda Bar <nojb@math.harvard.edu> wrote:
> Hello,
>
> I'm trying to build Ocaml 3.12.0 with native dynlink, but
> ./configure refuses to do so. Is native dynlink working? I'm trying
> this on a 32bit X86 running OS X.
I am not familiar with the ugly details of MacOSX.
I would imagine that native dynlinking requires a system with dlopen, and perhaps ELF format.
Perhaps there are some tricks on MacOSX to give you a dlopen interface.
But perhaps native dynlinking is not working on MacOSX.
Regards.
PS. A similar problem is the support of GCC plugins. AFAIK, MacOSX don't have them because of lack of native dlopen (but Macos provides an "emulation", I leave you to learn the details).
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
next prev parent reply other threads:[~2011-02-05 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 19:03 Nicolas Ojeda Bar
2011-02-05 19:21 ` Basile Starynkevitch [this message]
2011-02-05 19:42 ` Joel Reymont
[not found] ` <300769D8-9CD2-49F8-A398-F6AE659861BB@math.harvard.edu>
[not found] ` <0BC465F5-96AC-4326-8151-BE6795067156@gmail.com>
[not found] ` <FE132A19-256E-409E-B421-5BAE086AC8DB@math.harvard.edu>
2011-02-06 11:17 ` Joel Reymont
[not found] <201102061100.p16B00dj028912@walapai.inria.fr>
2011-02-06 11:15 ` CUOQ Pascal
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=20110205202152.6dd14cbf.basile@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=caml-list@yquem.inria.fr \
--cc=nojb@math.harvard.edu \
/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).