public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "earnie at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/45749] Response file unwrapped between collect2.exe and ld.exe
Date: Fri, 08 Feb 2013 17:58:00 -0000 [thread overview]
Message-ID: <bug-45749-4-8sBn5RMhBX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45749-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45749
Earnie <earnie at users dot sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |earnie at users dot
| |sourceforge.net
--- Comment #11 from Earnie <earnie at users dot sourceforge.net> 2013-02-08 17:58:03 UTC ---
So why is this doing the correct thing when supplying the --with-gnu-ld option
versus the fact that we have GNU ld and the configure script discovers it? It
seems to me the bug would be in the configure process.
next prev parent reply other threads:[~2013-02-08 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45749-4@http.gcc.gnu.org/bugzilla/>
2010-10-21 18:40 ` pinskia at gcc dot gnu.org
2013-02-08 17:58 ` earnie at users dot sourceforge.net [this message]
2022-01-01 7:31 ` pinskia at gcc dot gnu.org
2022-09-22 10:00 ` redi at gcc dot gnu.org
2022-11-18 3:55 ` pinskia at gcc dot gnu.org
2023-06-14 18:25 ` costas.argyris at gmail dot com
2010-09-22 16:28 [Bug c++/45749] New: " bogus2 at arc dot net dot au
2010-09-22 16:42 ` [Bug driver/45749] " pinskia at gcc dot gnu dot org
2010-09-22 16:42 ` pinskia at gcc dot gnu dot org
2010-09-22 16:58 ` bogus2 at arc dot net dot au
2010-09-22 17:17 ` bogus2 at arc dot net dot au
2010-09-22 17:42 ` pinskia at gcc dot gnu dot org
2010-09-22 19:57 ` rguenth at gcc dot gnu dot org
2010-09-22 19:59 ` rguenth at gcc dot gnu dot org
2010-09-22 20:10 ` bogus2 at arc dot net dot au
2010-09-22 20:16 ` bogus2 at arc dot net dot au
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-45749-4-8sBn5RMhBX@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).