From: Paul Bristow <paul@cee.hw.ac.uk>
To: caml-list@inria.fr
Subject: Objective Caml 2 with RedHat 5.1
Date: Wed, 14 Oct 1998 16:05:24 +0100 [thread overview]
Message-ID: <3624BDB3.82231609@cee.hw.ac.uk> (raw)
Hi,
I've recently upgraded to RedHat (Linux) 5.1 and am having problems, I
was wondering if anyone else has had exeperience with RH5.1 so I can
identify whether my problems are to do with RH5.1 or with my local
setup.
First off I tried to simply 'configure' as follows:
./configure -bindir $DEPOT/dsg/local/arch.linux/bin -libdir
$DEPOT/dsg/local/arc
h.linux/lib/ocaml -mandir $DEPOT/dsg/local/man/man1 -cc gcc -x11include
/usr/X11
R6/include -x11lib /usr/X11R6/lib
This all worked fine.
Then I did make world and got:
make[1]: Entering directory
`/a/azdak/root/depot0/.primary/dsg/local/src/ocaml-2.00/byterun'
sed -n -e '/^ /s/ \([A-Z]\)/ \&\&lbl_\1/gp' \
-e '/^}/q' instruct.h > jumptbl.h
gcc -O -fno-defer-pop -Wall -c interp.c -o interp.o
interp.c: In function `interprete':
interp.c:151: warning: `pc' might be used uninitialized in this function
interp.c:151: warning: variable `pc' might be clobbered by `longjmp' or
`vfork'
interp.c:152: warning: `sp' might be used uninitialized in this function
interp.c:152: warning: variable `sp' might be clobbered by `longjmp' or
`vfork'
interp.c:153: warning: `accu' might be used uninitialized in this
function
interp.c:153: warning: variable `accu' might be clobbered by `longjmp'
or `vfork'
interp.c:166: warning: `env' might be used uninitialized in this
function
interp.c:166: warning: variable `env' might be clobbered by `longjmp' or
`vfork'
interp.c:167: warning: `extra_args' might be used uninitialized in this
function
interp.c:167: warning: variable `extra_args' might be clobbered by
`longjmp' or `vfork'
interp.c:168: warning: `initial_external_raise' might be used
uninitialized in this function
interp.c:168: warning: variable `initial_external_raise' might be
clobbered by `longjmp' or `vfork'
interp.c:169: warning: `initial_sp_offset' might be used uninitialized
in this function
interp.c:169: warning: variable `initial_sp_offset' might be clobbered
by `longjmp' or `vfork'
interp.c:983: fixed or forbidden register was spilled.
This may be due to a compiler bug or to impossible asm
statements or clauses.
make[1]: *** [interp.o] Error 1
make[1]: Leaving directory
`/a/azdak/root/depot0/.primary/dsg/local/src/ocaml-2.00/byterun'
make: *** [coldstart] Error 2
So I checked my compiler:
gcc -v
Reading specs from /usr/lib/gcc-lib/i586-linux/egcs-2.90.29/specs
gcc version egcs-2.90.29 980515 (egcs-1.0.3 release)
I suspect this is the problem. Has anyone else succesfully compiled
with egcs?
n.b. I remembered to use sh and not csh or other.
Thanks,
--
Paul C Bristow,
Dept. Computing & Elec. Eng. Heriot-Watt University, Edinburgh EH14 4AS.
Phone: (+44) 131 451 5111 ext 4179. e-mail: paul@cee.hw.ac.uk
"Smith and Wesson, the ultimate point and click interface!"
next reply other threads:[~1998-10-15 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-14 15:05 Paul Bristow [this message]
1998-10-15 17:17 ` Xavier Leroy
1998-10-16 0:05 ` David Monniaux
1998-10-16 0:54 ` building ocaml-2.00 with egcs Jens-Ulrik Petersen
1998-10-16 23:33 ` building ocaml-2.00 with gcc-2.7.2.3 Jens-Ulrik Petersen
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=3624BDB3.82231609@cee.hw.ac.uk \
--to=paul@cee.hw.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