public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/38251] [4.4 Regression] tools.zip doesn't build on systems with short command lines Date: Mon, 24 Nov 2008 18:29:00 -0000 [thread overview] Message-ID: <20081124182939.22770.qmail@sourceware.org> (raw) In-Reply-To: <bug-38251-279@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from aph at gcc dot gnu dot org 2008-11-24 18:29 ------- Yes, of course. jar has an update mode that adds files, so I can use that. How long may an arglist be? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38251
next prev parent reply other threads:[~2008-11-24 18:29 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-24 17:53 [Bug libgcj/38251] New: " ro at gcc dot gnu dot org 2008-11-24 17:56 ` [Bug libgcj/38251] " aph at gcc dot gnu dot org 2008-11-24 18:04 ` ro at techfak dot uni-bielefeld dot de 2008-11-24 18:29 ` aph at gcc dot gnu dot org [this message] 2008-11-24 18:37 ` ro at techfak dot uni-bielefeld dot de 2008-11-24 18:48 ` aph at gcc dot gnu dot org 2008-11-24 18:52 ` aph at gcc dot gnu dot org 2008-11-25 16:33 ` rguenth at gcc dot gnu dot org 2009-04-21 15:54 ` [Bug libgcj/38251] [4.4/4.5 " jakub at gcc dot gnu dot org 2009-07-22 10:33 ` jakub at gcc dot gnu dot org 2009-07-28 17:53 ` htl10 at users dot sourceforge dot net 2009-07-28 18:06 ` htl10 at users dot sourceforge dot net 2009-07-28 20:30 ` htl10 at users dot sourceforge dot net 2009-07-28 20:42 ` htl10 at users dot sourceforge dot net 2009-07-29 8:20 ` ro at techfak dot uni-bielefeld dot de 2009-10-15 12:53 ` jakub at gcc dot gnu dot org 2010-01-21 13:15 ` jakub at gcc dot gnu dot org 2010-03-01 12:32 ` ro at gcc dot gnu dot org 2010-03-01 18:15 ` ro at gcc dot gnu dot org 2010-03-01 18:15 ` ro at gcc dot gnu dot org 2010-06-02 16:57 ` ro at gcc dot gnu dot 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=20081124182939.22770.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).