public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/45760] GCC build fails: can't find MPC
Date: Thu, 23 Sep 2010 14:08:00 -0000	[thread overview]
Message-ID: <20100923140819.8690.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45760-19725@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from redi at gcc dot gnu dot org  2010-09-23 14:08 -------
GCC doesn't set runpaths in executables, this is intentional:
http://gcc.gnu.org/faq.html#rpath

If you don't want those support libs installed for their own sake and are only
installing them for GCC to use, then a simpler way to build it is to put the
gmp, mpfr and mpc sources under gcc-4.5.1 (renamed from gmp-x.y.z to just gmp,
and similarly for mpfr and mpc) and then just configure gcc without any
--with-{gmp,mpfr,mpc} options.  That way gcc will build with those sources and
doesn't need to find the shared libs.

Or you can build the libs with --disable-shared so that gcc will have to link
statically to libgmp.a, which also avoids needing to find the shared libs.

Or you can just make sure the shared lib can be found, using LD_LIBRARY_PATH or
LD_RUN_PATH or ldconfig.

(In reply to comment #0)
> But libmpc.so.2 is there. I even took care of creating artificial symbolic
> links to satisfy this bizarre 'powerpc64-unknown-linux-gnu' under ROOT.

Don't do that.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45760


  parent reply	other threads:[~2010-09-23 14:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 13:07 [Bug other/45760] New: " avi at unix dot sh
2010-09-23 13:58 ` [Bug other/45760] " redi at gcc dot gnu dot org
2010-09-23 14:04 ` avi at unix dot sh
2010-09-23 14:08 ` redi at gcc dot gnu dot org [this message]
2010-09-23 14:15 ` [Bug bootstrap/45760] " redi at gcc dot gnu dot org
2010-09-23 14:46 ` avi at unix dot sh
2010-09-23 14:47 ` avi at unix dot sh
2010-09-23 15:28 ` redi at gcc dot gnu dot org
2010-09-23 15:28 ` redi at gcc dot gnu dot org

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=20100923140819.8690.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).