From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] prelinking ocamlfind
Date: Mon, 19 Jul 2004 15:48:46 +0200 [thread overview]
Message-ID: <20040719134845.GB30112@yquem.inria.fr> (raw)
In-Reply-To: <20040717150442.GA25514@pegasos>
> Xavier, i have been told that this probably happens because we use a elf
> section that is normally strippable.
It's even worse than that, but I won't get into details :-)
> It could be solved by using a
> special elf section specialized to our need (maybe one named bytecode or
> something), then at least strip and possibly the prelink stuff, would
> not remove it as it does not.
Yes, but:
- This solution is not portable to non-ELF platforms (e.g. MS Windows),
thus forcing an unpleasant fork in the code.
- The ELF format is very complex. There are libraries that facilitate
manipulations of ELF files (e.g. libelf), but these are not
universally available and severely under-documented.
Rather than muck with ELF, a simpler solution would be to embed the
bytecode executable as initialized C arrays in the executable
generated by ocamlc -custom. That's what ocamlc -output-obj does, and
I believe it shouldn't be too hard to adapt the existing -output-obj
code to the -custom case.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-07-19 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 14:53 Leo Rozenberg
2004-07-16 14:47 ` Xavier Leroy
2004-07-17 15:04 ` Sven Luther
2004-07-19 13:48 ` Xavier Leroy [this message]
2004-07-20 3:31 ` Sven Luther
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=20040719134845.GB30112@yquem.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=sven.luther@wanadoo.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).