caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: Chris Hecker <checker@d6.com>
Cc: Yang Shouxun <yangsx@fltrp.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Error during partial linking
Date: Tue, 22 Oct 2002 19:00:56 +0200	[thread overview]
Message-ID: <20021022190056.A28301@pauillac.inria.fr> (raw)
In-Reply-To: <4.3.2.7.2.20021022090136.035ec2f8@mail.d6.com>; from checker@d6.com on Tue, Oct 22, 2002 at 09:07:00AM -0700

> >+ /usr/bin/objcopy --redefine-sym
> >'WeightBalancedSet__zero_227=Baire__WeightBalancedSet__zero_227' [...]
> >--redefine-sym 'AmortizedQueue=Baire__AmortizedQueue' 'baire.o'
> >Error during partial linking
> >make[1]: *** [nativepack] Error 2
> 
> I think this is the command line length limit problem, for which there is a 
> FIXME comment in the asmcomp/asmpackager.ml.

This is also my guess, although I was expecting an error message to be
printed by the shell (but then it's perhaps system() itself that
fails).  I'll fix this length limit issue soon in the CVS version.
Too bad objcopy cannot take its symbol redefinitions from a file...

Coming back to your initial desire to "pack" Baire (if I may say so),
I would very strong advise Diego to name his "List" module something
else, to avoid conflict with the standard library module of the same
name.  The hypothesis that compilation units are identified by unique
names is really essential to the way the OCaml compilers work.  I know
it's sometimes an annoyance (all cool names are already taken by the
standard lib :-), but you're really going to run into trouble with
name conflicts.

- 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


  reply	other threads:[~2002-10-22 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  5:33 Yang Shouxun
2002-10-22  8:42 ` Xavier Leroy
2002-10-22  9:21   ` Sven Luther
2002-10-22 16:17     ` Chris Hecker
2002-10-22 16:47       ` Sven Luther
2002-10-22 17:14     ` [Caml-list] on the -pack option Xavier Leroy
2002-10-22 19:30       ` Sven Luther
2002-10-22  9:37   ` [Caml-list] Error during partial linking Yang Shouxun
2002-10-22 16:07     ` Chris Hecker
2002-10-22 17:00       ` Xavier Leroy [this message]
2002-10-22 17:12         ` Chris Hecker
2002-10-22 17:21         ` brogoff
2002-10-22 20:06           ` Dmitry Bely
2002-10-22 20:25             ` Alain Frisch
2002-10-22 20:37               ` Dmitry Bely
2002-10-22 20:53                 ` Alain Frisch
2002-10-22 21:10                   ` Dmitry Bely
2002-10-23  7:15                 ` Alessandro Baretta
     [not found]         ` <Pine.LNX.4.44.0210221008100.6093-100000@grace.speakeasy.ne t>
2002-10-22 17:44           ` Chris Hecker
2002-10-22 19:31         ` Sven Luther
2002-10-22 23:38           ` Chris Hecker
2002-10-23  4:16             ` David Brown
2002-10-23 10:01           ` Diego Olivier Fernandez Pons
2002-10-23 10:36             ` Sven Luther
2002-10-23 11:41               ` Alessandro Baretta

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=20021022190056.A28301@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=checker@d6.com \
    --cc=yangsx@fltrp.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).