Re: [Caml-list] Error during partial linking

[Chris Hecker <checker@d6.com>]

> > >Error during partial linking
> > 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).

Yes, it failed anonymously for me as well (on freebsd, when I was testing 
my win32 patch...this is a reminder to reply to my mail to you about that, 
too :).

>I'll fix this length limit issue soon in the CVS version.
>Too bad objcopy cannot take its symbol redefinitions from a file...

Yep, all programs should be able to take a response file for arguments.

>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.

We just need to pack the standard library and be done with it, and then it 
will finally liberate all of those common names for user programs!  It's 
the Right Thing.  :)

Hmm, now that I think about it, the native code pack could just shove any 
dependent C obj/lib files into the packed object as well, truly doing away 
with any external files.  Maybe it already does this...

Chris


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