From: Bill Smith <sesquized@sbcglobal.net>
To: caml-list@yquem.inria.fr
Subject: gcc 4.0.0 and OCaml 3.08.3
Date: Sun, 22 May 2005 08:53:33 -0500 [thread overview]
Message-ID: <6.2.1.2.0.20050522085211.01de9150@pop.sbcglobal.yahoo.com> (raw)
I've been having trouble with the "make world" phase of compiling OCaml
3.08.3 with gcc 4.0.0.
I'm using Linux 2.4.26 on an AMD Athlon XP.
There error I get is:
/gcc-4.0.0/bin/gcc -O2 -O -I../../byterun -D_FILE_OFFSET_BITS=64
-D_REENTRANT -fPIC -DBNG_ARCH_ia32 -DBNG_ASM_LEVEL=2 -c -o bng.o bng.c
In file included from bng.c:21:
bng_ia32.c: In function 'bng_ia32_mult_add_digit':
bng_ia32.c:111: error: can't find a register in class 'GENERAL_REGS' while
reloading 'asm'
make[1]: *** [bng.o] Error 1
To deal with the problem I've just fallen back to gcc 3.4.3 which compiles
ocaml 3.08.3 successfully.
Bill Smith
next reply other threads:[~2005-05-22 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 13:53 Bill Smith [this message]
2005-05-25 9:11 ` [Caml-list] " Sven Luther
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=6.2.1.2.0.20050522085211.01de9150@pop.sbcglobal.yahoo.com \
--to=sesquized@sbcglobal.net \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).