public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bogus2 at arc dot net dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/45749] New: Response file unwrapped between collect2.exe and ld.exe Date: Wed, 22 Sep 2010 16:28:00 -0000 [thread overview] Message-ID: <bug-45749-19722@http.gcc.gnu.org/bugzilla/> (raw) When compiling on MinGW under cmd.exe it's necessary to use @FILE to work around the 32k limit on arguments when linking a large number of objects. Unfortunately for some reason collect2.exe does not forward the file to ld.exe but instead appears to send its contents as arguments to CreateProcess() leading to the error: collect2: CreateProcess: No such file or directory Which is the typically unhelpful way for Windows to report this problem and something that led me on a 4 day goose-chase looking for the "missing" file or directory. Really if I tell collect2 to use a response file it's absolutely essential it uses it internally or else finds some other way around the 32k barrier (like piping to stdin). -- Summary: Response file unwrapped between collect2.exe and ld.exe Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bogus2 at arc dot net dot au http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45749
next reply other threads:[~2010-09-22 16:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-22 16:28 bogus2 at arc dot net dot au [this message] 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-19722@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).