public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Dennis Clarke" <dclarke@blastwave.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 4.2.3 : make: *** [bootstrap] Error 2
Date: Wed, 12 Mar 2008 05:24:00 -0000	[thread overview]
Message-ID: <m3ejag1pmz.fsf@google.com> (raw)
In-Reply-To: <2119.72.39.133.97.1205265745.squirrel@mail.blastwave.org> (Dennis Clarke's message of "Tue\, 11 Mar 2008 16\:02\:25 -0400 \(EDT\)")

"Dennis Clarke" <dclarke@blastwave.org> writes:

> Both GMP and MPFR are built and pass all tests and the libraries are created
> fine :
>
> gmp-4.2.2
> mpfr-2.3.1
>
> dclarke@vesta:~/build/first_pass/gcc/gcc-4.2.3-build$ ls -lap
> $HOME/local/lib | grep -E "gmp|mpfr"
> -rw-r--r--  1 dclarke csw  592016 Mar  9 17:48 libgmp.a
> -rwxr-xr-x  1 dclarke csw     794 Mar  9 17:48 libgmp.la
> lrwxrwxrwx  1 dclarke csw      15 Mar  9 17:48 libgmp.so -> libgmp.so.3.4.2
> lrwxrwxrwx  1 dclarke csw      15 Mar  9 17:48 libgmp.so.3 -> libgmp.so.3.4.2
> -rwxr-xr-x  1 dclarke csw  317869 Mar  9 17:48 libgmp.so.3.4.2
> -rw-r--r--  1 dclarke csw 1812424 Mar  9 22:06 libmpfr.a
> -rwxr-xr-x  1 dclarke csw     985 Mar  9 22:06 libmpfr.la
> lrwxrwxrwx  1 dclarke csw      16 Mar  9 22:06 libmpfr.so -> libmpfr.so.1.1.1
> lrwxrwxrwx  1 dclarke csw      16 Mar  9 22:06 libmpfr.so.1 -> libmpfr.so.1.1.1
> -rwxr-xr-x  1 dclarke csw  985371 Mar  9 22:06 libmpfr.so.1.1.1


You will do better to use --disable-shared when you configure gmp and
mpfr.  Using the shared libraries means that you need to ensure that
gcc can find them at runtime, and that typically requires setting
LD_LIBRARY_PATH.


> /home/dclarke/local/powerpc-unknown-linux-gnu/sys-include accepts -g... no
> checking whether the GNU Fortran compiler is working... no
> configure: error: GNU Fortran is not working; the most common reason for
> that is that you might have linked it to shared GMP and/or MPFR libraries,
> and not set LD_LIBRARY_PATH accordingly. If you suspect any other reason,
> please report a bug in http://gcc.gnu.org/bugzilla, attaching
> /home/dclarke/build/first_pass/gcc/gcc-4.2.3-build/powerpc-unknown-linux-gnu/libgfortran/config.log

There you go: set LD_LIBRARY_PATH to work around this, but even better
is to use static gmp and mpfr libraries.


> Should I just set LD_LIBRARY_PATH=$HOME/local/lib  ??

That will probably work too.

Ian

  reply	other threads:[~2008-03-12  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 20:03 Dennis Clarke
2008-03-12  5:24 ` Ian Lance Taylor [this message]
2008-03-12  5:35   ` Dennis Clarke
2008-03-12 12:24   ` Dennis Clarke
2008-03-14  1:26   ` Dennis Clarke

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=m3ejag1pmz.fsf@google.com \
    --to=iant@google.com \
    --cc=dclarke@blastwave.org \
    --cc=gcc-help@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).