From: Daniel Andor <da209@cam.ac.uk>
To: caml-list@inria.fr
Subject: [Caml-list] Build error on DEC Alpha
Date: Thu, 16 Aug 2001 23:32:53 +0100 [thread overview]
Message-ID: <20010816233253.A21097@prometheus.jesus.cam.ac.uk> (raw)
Hi,
I've been trying to build 3.02 on a Tru64 box. I can't use the native code
compiler to link. I'm new to the list, so apologies if this has been
reported/fixed already (brief search in archive showed naught).
It seems the problem only occurs when trying to link to a library.
Platform details:
$ cc -V
Compaq C V6.3-027 on Compaq Tru64 UNIX V5.1 (Rev. 732)
Compiler Driver V6.3-026 (sys) cc Driver
$ uname -a
OSF1 tcm18.phy.cam.ac.uk V5.1 732 alpha
Error details:
$ cat trivial.ml
print_int 5;;
$ ocamlopt trivial.ml -o go; ./go
5$ cat trivial2.ml
Printf.printf "%d" 5;;
$ ocamlopt trivial2.ml -c
$ ocamlopt trivial2.ml -o go
ld:
/temp/usr/local/lib/ocaml/stdlib.a(array.o): branch to shared library symbol
'__divq' will cause unpredictable behavior.
/temp/usr/local/lib/ocaml/stdlib.a(array.o): branch relocation out-of-range,
bad object file produced, can't branch from 0x120013e34 to 0x3ff800f062c
[snip more of the same]
Error during linking
$
Error details on make opt.opt:
ld:
typing/printtyp.o: branch to shared library symbol '__divq' will cause
unpredictable behavior.
typing/printtyp.o: branch relocation out-of-range, bad object file produced,
can't branch from 0x1201067b0 to 0x3ff800f062c
typing/printtyp.o: branch to shared library symbol '__remq' will cause
unpredictable behavior.
typing/printtyp.o: branch relocation out-of-range, bad object file produced,
can't branch from 0x1201067f8 to 0x3ff801148bc
[snip -- lots more of the same]
Error during linking
*** Exit 2
Stop.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
reply other threads:[~2001-08-16 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010816233253.A21097@prometheus.jesus.cam.ac.uk \
--to=da209@cam.ac.uk \
--cc=caml-list@inria.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