From: John Carr <jfc@MIT.EDU>
To: Dale Harris <rodmur@maybe.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Compiling on Solaris 64 bit
Date: Wed, 03 Nov 2004 17:38:23 -0500 [thread overview]
Message-ID: <200411032238.iA3McNl4008481@scrubbing-bubbles.mit.edu> (raw)
In-Reply-To: Your message of "Wed, 03 Nov 2004 14:02:05 PST." <20041103220205.GA28822@maybe.org>
> I've been trying unsuccessfully to compile ocaml on a Solaris 9 system,
> SunFire v880z, at 64 bits. I'm trying to use the SUNWspro C compiler
> with the "-fast -xarch=v9b" or just "-xarch=v9b" options. I get the
> following result:
>
> cp yacc/ocamlyacc boot/ocamlyacc
> cd stdlib; make COMPILER=../boot/ocamlc all
> make[1]: Entering directory `/home/rodmur/src/ocaml/ocaml-3.07/stdlib'
> ../boot/ocamlrun ../boot/ocamlc -g -warn-error A -nostdlib -nopervasives
> -c pervasives.mli
> make[1]: *** [pervasives.cmi] Segmentation Fault (core dumped)
> make[1]: Leaving directory `/home/rodmur/src/ocaml/ocaml-3.07/stdlib'
> make: *** [coldstart] Error 2
I have patches to make ocamlopt generate 64 bit code:
<http://www.mit.edu/~jfc/ocaml-3.08.1-sparc64.tar.gz>.
My changes only affect native code. Byte code (ocamlrun) should work
in 32 or 64 bit mode with no source changes. Maybe upgrading to 3.08
will help. The Makefiles automatically add "-O" to the compiler
options so in your case there isn't much difference with or without
-fast. You might try v9 or v9a instead of v9b just in case there
is a code generation bug.
--John Carr (jfc@mit.edu)
prev parent reply other threads:[~2004-11-03 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 22:02 Dale Harris
2004-11-03 22:38 ` John Carr [this message]
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=200411032238.iA3McNl4008481@scrubbing-bubbles.mit.edu \
--to=jfc@mit.edu \
--cc=caml-list@inria.fr \
--cc=rodmur@maybe.org \
/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).