caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
	malc <malc@pulsesoft.com>,
	Oliver Bandel <oliver@first.in-berlin.de>,
	caml-list@inria.fr
Subject: Re: [Caml-list] "No bytecode specified"
Date: Mon, 26 Aug 2002 14:53:01 +0200	[thread overview]
Message-ID: <20020826125301.GB4254@iliana> (raw)
In-Reply-To: <20020826120031.A28824@pauillac.inria.fr>

On Mon, Aug 26, 2002 at 12:00:31PM +0200, Xavier Leroy wrote:
> > Alternatively, strip can be fixed to know about ocaml bytecode.
> 
> I wouldn't recommend that -- if I were the maintainer of "strip", I'd
> scream at such a kludge :-)

:)))

That said, maybe strip has a list of things not to strip or something
such ?

> > I was also told that if the ocaml team would have used another
> > label/tag/whatever it is called in the binary code than the one it is
> > using, then strip would know about it.
> 
> Yes, a cleaner solution would be to embed the OCaml bytecode in a
> special ELF section.  But there are two problems with this: 1- the ELF
> file format is quite complex, and 2- this solution would break utterly
> on non-ELF systems, e.g. Windows.

Ok, you know a lot more than me about this, but couldn't it not be
possible to implement this only on ELF systems ?
Anyway, the resulting code is arch/system dependant, since you embed
it with ocamlrun anyway, is it not ?

> The current solution (just stick the bytecode at the end of the native
> executable) is a hack, but it's a hack that works on *every single
> platform* I've tested in the last 12 years...

Sure, a good reason for it i guess, but the result is that strip breaks
ocaml bytecode executables.

Friendly,

Sven Luther
-------------------
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


  reply	other threads:[~2002-08-27  6:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 20:50 Oliver Bandel
2002-08-25 23:39 ` Stefano Zacchiroli
2002-08-26  7:32 ` malc
2002-08-26  8:38   ` Sven LUTHER
2002-08-26 10:00     ` Xavier Leroy
2002-08-26 12:53       ` Sven LUTHER [this message]
2002-08-26 11:03     ` malc
2002-08-26 12:32   ` Oliver Bandel
2002-08-26 12:36   ` Oliver Bandel
     [not found]   ` <Pine.LNX.3.95.1020826143546.418B-100000@first.in-berlin.de >
2002-08-27  1:52     ` Chris Hecker
2002-09-03 12:32 ` Oliver Bandel
2002-09-03 13:16   ` Xavier Leroy
2002-09-03 13:34     ` Oliver Bandel

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=20020826125301.GB4254@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=malc@pulsesoft.com \
    --cc=oliver@first.in-berlin.de \
    --cc=xavier.leroy@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).