From: overbored <overbored@overbored.net>
To: skaller@users.sourceforge.net
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Can't compile on Cygwin
Date: Mon, 27 Sep 2004 01:10:36 -0700 [thread overview]
Message-ID: <4157CAFC.8010707@overbored.net> (raw)
In-Reply-To: <1096271713.28613.454.camel@pelican.wigram>
What the...wow, sorry about that! That question actually pertained to
unison, not Ocaml. But since this is getting somewhere... :)
I'm a newbie to Ocaml so I wasn't entirely sure what to do but the only
file in unison that used format_int had the lines:
external format_int: string -> int -> string = "format_int"
external format_float: string -> float -> string = "format_float"
[format_int and format_float are used further down in the file]
So should I prepend "caml_" to both the stuff in quotes and the stuff on
the left? I did that and it compiled fine but I'm wondering if modifying
the stuff in quotes might cause problems later on.
Thanks!
skaller wrote:
> On Mon, 2004-09-27 at 16:54, overbored wrote:
>
>
>>ubase/uprintf.o(.text+0x29a):fake: undefined reference to `_format_int'
>>ubase/uprintf.o(.text+0x2fa):fake: undefined reference to `_format_float'
>
>
> Old version. I've had this problem on a Linux box too.
> Used to be 'format_int' and 'format_float' were builtin primitives,
> that is, C functions.
>
> All C primitives in Ocaml 3.08 now have a prefix 'caml_'
> to avoid namespace clashes:
>
> stdlib/pervasives.ml:external format_int: string -> int -> string =
> "caml_format_int"
>
-------------------
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-09-27 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 6:54 overbored
2004-09-27 7:55 ` skaller
2004-09-27 8:10 ` overbored [this message]
2004-09-27 9:16 ` skaller
2004-09-27 9:43 ` Damien Doligez
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=4157CAFC.8010707@overbored.net \
--to=overbored@overbored.net \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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