caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Damien Doligez <Damien.Doligez@inria.fr>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] state of native dynlink on os x
Date: Tue, 28 Feb 2012 16:34:55 +0100	[thread overview]
Message-ID: <8FFF332E-3635-467F-B135-F09F806A034E@polytechnique.org> (raw)
In-Reply-To: <AA6DC537-C741-49CF-95F4-B5D71043078A@inria.fr>

On 27 févr. 2012, at 16:43, Damien Doligez wrote:

> Hi Alan,
>> Following a suggestion by Daniel Bünzli, I used the minimum example from http://caml.inria.fr/mantis/view.php?id=5093 then I can see that native dynlink does work.
>> 
>> However two questions remain. I get `ld: warning: -read_only_relocs cannot be used with x86_64` each time I link natively. Does this mean I should reopen http://caml.inria.fr/mantis/view.php?id=4863 (the patch there is applied to my version of caml)?
> 
> Which version of Mac OS X, which version of OCaml, and what is the output of configure?

OS X 10.7.3, ocaml 3.12.1-godi2. About the output of configure, I'm trying to see how to get it from godi, in the meantime here is my ocamlc -config:

version: 3.12.1
standard_library_default: /Users/schmitta/godi/lib/ocaml/std-lib
standard_library: /Users/schmitta/godi/lib/ocaml/std-lib
standard_runtime: /Users/schmitta/godi/bin/ocamlrun
ccomp_type: cc
bytecomp_c_compiler: gcc -fno-defer-pop -no-cpp-precomp -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
bytecomp_c_libraries: -lcurses -lpthread
native_c_compiler: gcc -D_FILE_OFFSET_BITS=64 -D_REENTRANT
native_c_libraries: 
native_pack_linker: ld -r -arch x86_64  -o 
ranlib: ranlib
cc_profile: -pg
architecture: amd64
model: default
system: macosx
asm: as -arch x86_64
ext_obj: .o
ext_asm: .s
ext_lib: .a
ext_dll: .so
os_type: Unix
default_executable_name: a.out
systhread_supported: true


>> Also, when running why3, I get some undefined symbols (_camlRandom, _camlParsing, _camlString). Where are these symbols defined?
> 
> Looks like modules of the standard library, right ?

Do they need to be loaded manually, or should they be loaded automatically by the native linker?

Alan

  parent reply	other threads:[~2012-02-28 15:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 11:17 Alan Schmitt
2012-02-15 12:34 ` Daniel Bünzli
2012-02-15 14:16   ` Alan Schmitt
2012-02-17  6:47 ` Alan Schmitt
2012-02-27 15:43   ` Damien Doligez
2012-02-27 17:49     ` Pierre-Alexandre Voye
2012-02-28 10:15       ` David MENTRE
2012-02-28 10:32         ` Pierre-Alexandre Voye
2012-02-28 15:34     ` Alan Schmitt [this message]
2012-02-29  8:33       ` Alan Schmitt
2012-03-07 10:55       ` Damien Doligez
2012-03-07 15:14         ` Alan Schmitt
2012-03-08 11:13     ` Alan Schmitt
2012-03-08 14:16       ` Alan Schmitt
2012-03-08 14:23         ` Pierre-Alexandre Voye
2012-03-08 14:35           ` Alan Schmitt
2012-03-08 15:50             ` Pierre-Alexandre Voye
2012-03-08 16:19               ` Jérémie Dimino
2012-03-08 16:16         ` Gabriel Scherer
2012-03-08 16:25           ` Jérémie Dimino
2012-03-08 16:31             ` Alan Schmitt

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=8FFF332E-3635-467F-B135-F09F806A034E@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=Damien.Doligez@inria.fr \
    --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).