caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: jonathan.roewen@gmail.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Using OCaml in a kernel
Date: Sat, 11 Dec 2004 08:00:36 +0900 (JST)	[thread overview]
Message-ID: <20041211.080036.25909489.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <ad8cfe7e04121013265eff7d60@mail.gmail.com>

From: Jonathan Roewen <jonathan.roewen@gmail.com>

> I've tried manually compiling libasmrun.a, but I'm getting some
> strange unresolved symbols to caml functions/declarations.
> 
> startup.o:
>  caml_data_segments
>  caml_code_segments
> i386.o
>  caml_program
>  caml_apply2
>  caml_apply3
> fail.o:
>  caml_exn_Failure (basically whole lot from the struct with these in it)
>  caml_bucket_Out_of_memory
>  caml_bucket_Stack_overflow
> roots.o:
>  caml_frametable
>  caml_globals

These symbols are defined at link time by the ocamlopt compiler.
You can get the assembler code defining them by using the -dstartup
option of ocamlopt while linking; it will show up in a
/tmp/camlstartup????.s file.
Note of course that some of these definitions are specific for each
program.

Jacques Garrigue


  reply	other threads:[~2004-12-10 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06  0:48 Jonathan Roewen
2004-12-06  1:03 ` [Caml-list] " Sachin Shah
2004-12-06  8:09 ` Ville-Pertti Keinonen
2004-12-10 21:26   ` Jonathan Roewen
2004-12-10 23:00     ` Jacques Garrigue [this message]
2004-12-14  1:43       ` Jonathan Roewen
2004-12-14  9:09         ` Ville-Pertti Keinonen
2004-12-14 18:10           ` Jonathan Roewen
2004-12-15  2:03             ` skaller
2004-12-28 22:35       ` Jonathan Roewen
2004-12-06  9:08 ` Vincenzo Ciancia
2004-12-06 10:00 ` Frédéric Gava

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=20041211.080036.25909489.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@yquem.inria.fr \
    --cc=jonathan.roewen@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;
as well as URLs for NNTP newsgroup(s).