public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "john.soo+gcc-bugzilla at arista dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/86030] specs file processing does not create response files for input directories Date: Sun, 17 Sep 2023 15:47:50 +0000 [thread overview] Message-ID: <bug-86030-4-wgEWBgERVH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-86030-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86030 --- Comment #19 from John Soo <john.soo+gcc-bugzilla at arista dot com> --- I verified the proposed patch sent argv through @file, but COLLECT_GCC_OPTIONS still caused E2BIG. In the failing execve, COLLECT_GCC_OPTIONS was 134227 characters long.
next prev parent reply other threads:[~2023-09-17 15:47 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-86030-4@http.gcc.gnu.org/bugzilla/> 2021-05-19 10:43 ` redi at gcc dot gnu.org 2023-06-14 18:27 ` costas.argyris at gmail dot com 2023-09-09 16:17 ` john.soo+gcc-bugzilla at arista dot com 2023-09-09 16:35 ` costas.argyris at gmail dot com 2023-09-09 19:59 ` john.soo+gcc-bugzilla at arista dot com 2023-09-10 20:50 ` john.soo+gcc-bugzilla at arista dot com 2023-09-11 3:49 ` john.soo+gcc-bugzilla at arista dot com 2023-09-11 8:34 ` costas.argyris at gmail dot com 2023-09-11 15:28 ` john.soo+gcc-bugzilla at arista dot com 2023-09-11 15:52 ` costas.argyris at gmail dot com 2023-09-13 20:20 ` john.soo+gcc-bugzilla at arista dot com 2023-09-14 12:55 ` john.soo+gcc-bugzilla at arista dot com 2023-09-15 19:22 ` john.soo+gcc-bugzilla at arista dot com 2023-09-16 15:45 ` john.soo+gcc-bugzilla at arista dot com 2023-09-17 5:47 ` john.soo+gcc-bugzilla at arista dot com 2023-09-17 15:47 ` john.soo+gcc-bugzilla at arista dot com [this message] 2023-09-19 1:54 ` john.soo+gcc-bugzilla at arista dot com
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-86030-4-wgEWBgERVH@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).