From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: "Christoph Höger" <christoph.hoeger@celeraone.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Manually linking generated native code
Date: Thu, 19 Jan 2017 13:11:20 +0100 [thread overview]
Message-ID: <1484827880.14465.105.camel@gerd-stolpmann.de> (raw)
In-Reply-To: <CAOazmvss9i2izHxjuZgJeF+2csRUva7=TMcLWKno_8UOYusCJA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1685 bytes --]
Am Donnerstag, den 19.01.2017, 10:44 +0100 schrieb Christoph Höger:
> Dear all,
>
> consider a simple test program:
>
> let _ = Printf.printf "Hello world!\n"
>
> I can generate the relevant assembly just fine, e.g.:
>
> ocamlopt -dstartup -S test.ml
> gcc -c a.out.startup.s -c
>
> But I cannot link it:
>
> gcc a.out.startup.o -L$(ocamlc -where) -lasmrun_shared
> ....
> a.out.startup.o(.data+0x6e8): error: undefined reference to
> 'camlStd_exit__frametable'
> collect2: Fehler: ld gab 1 als Ende-Status zurück
> distcc[9960] ERROR: compile (null) on localhost failed
>
> It seems that the whole Pervasives is missing (which is kind of
> expected).
>
> How do I link it, manually? Where are the relevant object files?
There's stdlib.a in the OCaml library directory.
This is not the only problem with your approach. The OCaml linker
generates a number of functions that are global to the whole OCaml
program (in particular currying helpers). These are first known at link
time and thus generated that late. AFAIK you cannot generate these
functions outside the linker step.
The only official way how to turn OCaml code into a linkable object is
described here: http://caml.inria.fr/pub/docs/manual-ocaml/intfc.html#s
%3Aembedded-code
Gerd
> > thanks,>
> Christoph>
>
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 2246 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-01-19 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 9:44 Christoph Höger
2017-01-19 10:05 ` Bernhard Schommer
2017-01-19 12:11 ` Gerd Stolpmann [this message]
2017-01-19 12:24 ` Christoph Höger
2017-01-19 13:10 ` Gerd Stolpmann
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=1484827880.14465.105.camel@gerd-stolpmann.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@celeraone.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