From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: Patrick.Loiseleur@lri.fr (Patrick Loiseleur)
Cc: monniaux@clipper.ens.fr, caml-list@inria.fr
Subject: Re: ocamldebug must not be stripped!
Date: Wed, 24 Jun 1998 17:49:02 +0100 (MET DST) [thread overview]
Message-ID: <199806241549.RAA17813@miss.wu-wien.ac.at> (raw)
In-Reply-To: <13711.22440.102506.717388@pc84.lri.fr> from "Patrick Loiseleur" at Jun 23, 98 09:22:16 am
Bonjour - Hello,
english version
---------------
Ah, I see... The only program of the ocaml-distribution compiled to
bytecode even if native code is desired is the debugger! I didn't
know this...
[from Patrick.Loiseleur@lri.fr]
> However, it must be possible to modify the Makefile in order
> to compile it in native code. Or is it a special reason that makes
> compilation of ocamldebug in native code not possible ?
Although it is probably not necessary to compile the debugger in native
code (it is fast enough, I think), I had a look on that, but did not
succeed to link everything after having manipulated the Makefile:
I replaced all occurrences of ".cmo" by ".cmx", ".cma" by ".cmxa"
and added some object files, that implement otherwise missing symbols,
to the linking process:
../byterun/meta.o
../byterun/stacks.o
../byterun/fix_code.o
../byterun/prims.o
../byterun/debugger.o
../byterun/array.o
../byterun/fail.o
Unfortunately, the files "fail.o" and "array.o" contain some symbols
that also exist in "libasmrun.a", which is implicitly linked against
the executable. I thought, it would not be very wise to hack any further
into the build process of the debugger, since I am content with the
debugger anyway...
version francaise(?)
--------------------
Ah, je comprends... Seulement le debugger est compilé en "bytecode", même
si on demande code natif! Je ne l'ai pas su...
[de Patrick.Loiseleur@lri.fr]
> A moins d'une raison particulière (mais laquelle) je pense qu'il est
> possible de compiler ce programme en natif si on le désire.
Je ne pense pas qu'il soit nécessaire de compiler le debugger en natif
(il est assez vite), mais je l'ai essayé (sans succès):
J'ai remplacé ".cmo" par ".cmx", ".cma" par ".cmxa" au "Makefile" et j'ai
ajouté les fichiers suivants (ils contiennent des symbols nécessaires)
pour "linkage":
../byterun/meta.o
../byterun/stacks.o
../byterun/fix_code.o
../byterun/prims.o
../byterun/debugger.o
../byterun/array.o
../byterun/fail.o
Malheuresement, les fichiers "fail.o" et "array.o" contiennent quelques
symbols qui aussi existent en "libasmrun.a", qui est implicitement
utilisé pendant "linkage". Je n'ai pas continué á chercher une solution -
je n'ai pas besoin d'un debugger plus vite...
Best regards - bien amicalement,
Markus
--
* Markus Mottl | University of Economics and *
* Department of Applied | Business Administration *
* Computer Science | Vienna, Austria *
* mottl@miss.wu-wien.ac.at | http://miss.wu-wien.ac.at/~mottl *
next parent reply other threads:[~1998-06-25 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13711.22440.102506.717388@pc84.lri.fr>
1998-06-24 16:49 ` Markus Mottl [this message]
1998-06-22 10:48 Markus Mottl
1998-06-25 9:43 ` Xavier Leroy
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=199806241549.RAA17813@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--cc=Patrick.Loiseleur@lri.fr \
--cc=caml-list@inria.fr \
--cc=monniaux@clipper.ens.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