public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avi at unix dot sh" <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:04:00 -0000	[thread overview]
Message-ID: <20100923140357.6501.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45760-19725@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from avi at unix dot sh  2010-09-23 14:03 -------
I was able to make it pass that stage explicitly setting the library path like
this:

gcc-build$ LD_LIBRARY_PATH=$HOME/OpenFOAM/lib make

I found this was not related to MPC since I moved to 4.4.4 (pre-MPC version of
GCC) and I got same problem with MPFR (another GCC dependency).

Since I'm already using --with-mpfr=DIRNAME, I was expecting that the library
path was being set automatically.

So I still consider this a weak point on the build system that could be
automatically managed.


-- 

avi at unix dot sh changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|blocker                     |normal


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


  parent reply	other threads:[~2010-09-23 14:04 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 [this message]
2010-09-23 14:08 ` redi at gcc dot gnu dot org
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=20100923140357.6501.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).