public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54304] linking stage picks up system mpfr instead of in-tree version
Date: Fri, 17 Aug 2012 20:56:00 -0000	[thread overview]
Message-ID: <bug-54304-4-WP26o6NwbS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54304-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Tobias Schlüter <tobi at gcc dot gnu.org> 2012-08-17 20:56:40 UTC ---
You don't need the -L flags for the in-tree libraries at all as you could just
put, say, "path_to_mpfr/libmpfr.a" on the command line.  I understand that this
might need some major Makefile surgery.

Anyway, a build without --with-libiconv-prefix=/opt/local succeeded, I have
updated my system in the meantime, so I can't investigate this further.  (The
iconv issue was of the type described e.g. here
<https://bugs.php.net/bug.php?id=52611>).

Anyway, I think this can be closed as INVALID unless you find the suggestion to
do away with -L for in-tree stuff worthwhile.


  parent reply	other threads:[~2012-08-17 20:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 19:06 [Bug bootstrap/54304] New: " tobi at gcc dot gnu.org
2012-08-17 19:14 ` [Bug bootstrap/54304] " pinskia at gmail dot com
2012-08-17 19:24 ` tobi at gcc dot gnu.org
2012-08-17 19:27 ` glisse at gcc dot gnu.org
2012-08-17 19:30 ` tobi at gcc dot gnu.org
2012-08-17 19:31 ` tobi at gcc dot gnu.org
2012-08-17 19:33 ` tobi at gcc dot gnu.org
2012-08-17 19:36 ` tobi at gcc dot gnu.org
2012-08-17 19:39 ` tobi at gcc dot gnu.org
2012-08-17 19:40 ` glisse at gcc dot gnu.org
2012-08-17 20:56 ` tobi at gcc dot gnu.org [this message]
2012-08-17 21:22 ` glisse at gcc dot gnu.org
2012-08-17 21:36 ` tobi at gcc dot gnu.org
2012-08-17 22:06 ` glisse at gcc dot gnu.org
2012-08-17 22:25 ` tobi at gcc dot gnu.org
2015-06-04 16:18 ` egall at gwmail dot gwu.edu
2015-06-04 17:01 ` pinskia at gcc dot gnu.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=bug-54304-4-WP26o6NwbS@http.gcc.gnu.org/bugzilla/ \
    --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).