public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rwild at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/46607] [4.6 Regression] libgfortran relocated install fails Date: Mon, 13 Dec 2010 16:57:00 -0000 [thread overview] Message-ID: <bug-46607-4-xKy9I6YXDp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46607-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46607 Ralf Wildenhues <rwild at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rwild at gcc dot gnu.org --- Comment #3 from Ralf Wildenhues <rwild at gcc dot gnu.org> 2010-12-13 16:57:27 UTC --- So is this only about the MinGW case? Because there, we should just fix libtool to not ever relink. The more general issue described in comment #1 is a long-standing limitation of libtool.
next prev parent reply other threads:[~2010-12-13 16:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-22 18:20 [Bug libfortran/46607] New: " jsm28 at gcc dot gnu.org 2010-11-23 10:01 ` [Bug libfortran/46607] " rguenth at gcc dot gnu.org 2010-12-07 11:09 ` jakub at gcc dot gnu.org 2010-12-07 13:25 ` joseph at codesourcery dot com 2010-12-13 16:57 ` rwild at gcc dot gnu.org [this message] 2010-12-13 18:40 ` joseph at codesourcery dot com 2011-01-20 22:07 ` aoliva at gcc dot gnu.org 2011-01-24 23:45 ` joseph at codesourcery dot com 2011-01-25 9:03 ` rwild at gcc dot gnu.org 2011-01-25 17:01 ` joseph at codesourcery dot com 2011-01-27 4:26 ` aoliva at gcc dot gnu.org 2011-01-27 18:06 ` joseph at codesourcery dot com 2011-01-28 9:11 ` aoliva 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-46607-4-xKy9I6YXDp@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: linkBe 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).