From: Margaret Doll <Margaret_Doll@brown.edu>
To: gcc@gcc.gnu.org
Subject: Re: make bootstrap and make not working for gcc-4.4.1
Date: Tue, 08 Sep 2009 14:01:00 -0000 [thread overview]
Message-ID: <D09BAEB6-9978-427C-80A0-C921977CBBD4@brown.edu> (raw)
In-Reply-To: <4AA29644.1010103@gmail.com>
With the addition of the definition the LD_LIBRARY_PATH, the
configuration, make bootstrap, make and make install
worked.
Thanks to everyone that gave me suggestions.
On Sep 5, 2009, at 12:48 PM, Dave Korn wrote:
> Margaret Doll wrote:
>
>> I was following the instructions on the build from
>> http://gcc.gnu.org/java/build-snapshot.html
>>
>> 5. Compile and install gcc/gcj/libgcj
>> $ cd compile
>> $ mkdir objdir
>> $ cd objdir
>> $ ../gcc/configure --enable-threads=posix --prefix=/home/joerg/gcc \
>> --enable-shared --enable-languages=c++,java \ --with-as=/opt/gnu/
>> bin/as
>> --with-ld=/opt/gnu/bin/ld
>> $ make bootstrap
>> $ make
>> $ make install
>
> ? I thought we weren't supposed to use "make bootstrap" any more,
> that it
> was the default you got from just running plain "make". I'd omit
> the "make
> bootstrap" and just go straight to the next line.
>
>> cd /usr/local/gcc-4.1.1
>> ./configure
>> ends in the error that I have the wrong version of mpfr.h. I am using
>> mpfr-2.4.1. The error log says that I should be using mpfr 2.3.2+
>
> Possibly you have an old version lying around and it's finding it
> first?
> Does it help if you add a suitable --with-mpfr= option? Otherwise
> you may
> have to reproduce the failing autoconf test to figure out why it
> thinks you
> have an outdated mpfr header.
>
>
> cheers,
> DaveK
prev parent reply other threads:[~2009-09-08 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 14:28 Margaret Doll
2009-09-04 14:39 ` Paolo Carlini
2009-09-04 14:42 ` Paolo Carlini
2009-09-04 16:08 ` Margaret Doll
2009-09-04 19:01 ` Fwd: " Margaret Doll
2009-09-04 19:13 ` Richard Guenther
2009-09-05 16:34 ` Dave Korn
2009-09-08 14:01 ` Margaret Doll [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=D09BAEB6-9978-427C-80A0-C921977CBBD4@brown.edu \
--to=margaret_doll@brown.edu \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).