public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug bootstrap/20155] [4.0 Regression] libgcj build fails with "execvp: /bin/sh: Argument list too long"
Date: Fri, 15 Jul 2005 00:30:00 -0000 [thread overview]
Message-ID: <20050715003051.28548.qmail@sourceware.org> (raw)
In-Reply-To: <20050222215734.20155.gerald@pfeifer.com>
------- Additional Comments From mark at codesourcery dot com 2005-07-15 00:30 -------
Subject: Re: [4.0 Regression] libgcj build fails with
"execvp: /bin/sh: Argument list too long"
bonzini at gcc dot gnu dot org wrote:
> ------- Additional Comments From bonzini at gcc dot gnu dot org 2005-07-14 08:55 -------
> Adding Mark so that he can judge the opportunity of a backport.
>
> Removing bug 21624 dependency, because it is indeed fixed on mainline. If bug
> 21624 were fixed the command line could be even shorter, but the current
> situation on mainline is enough.
I think it would be good to backport this patch, as bootstrap breakage
is obviously severe. However, I wouldn't want to force the Java people
to do something they don't think is safe. As long as the Java people
are comfortable with the backport, it's fine by me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20155
next prev parent reply other threads:[~2005-07-15 0:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 22:06 [Bug libgcj/20155] New: " gerald at pfeifer dot com
2005-02-23 1:06 ` [Bug libgcj/20155] " pinskia at gcc dot gnu dot org
2005-02-23 1:12 ` pinskia at gcc dot gnu dot org
2005-02-23 8:36 ` pinskia at gcc dot gnu dot org
2005-03-02 21:49 ` [Bug libgcj/20155] [4.0/4.1 Regression] " kcook at gcc dot gnu dot org
2005-03-02 21:49 ` pinskia at gcc dot gnu dot org
2005-03-05 18:04 ` [Bug libgcj/20155] [4.0 " pinskia at gcc dot gnu dot org
2005-03-05 18:04 ` [Bug libgcj/20155] [4.0/4.1 " cvs-commit at gcc dot gnu dot org
2005-03-05 19:46 ` [Bug libgcj/20155] [4.0 " cvs-commit at gcc dot gnu dot org
2005-03-05 19:50 ` pinskia at gcc dot gnu dot org
2005-03-06 20:15 ` cvs-commit at gcc dot gnu dot org
2005-03-06 22:41 ` [Bug libgcj/20155] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-03-06 22:44 ` cvs-commit at gcc dot gnu dot org
2005-04-05 21:41 ` [Bug bootstrap/20155] " mmitchel at gcc dot gnu dot org
2005-04-16 22:03 ` pinskia at gcc dot gnu dot org
2005-04-21 4:58 ` mmitchel at gcc dot gnu dot org
2005-04-26 2:43 ` htl10 at users dot sourceforge dot net
2005-04-26 3:18 ` htl10 at users dot sourceforge dot net
2005-05-17 14:42 ` bonzini at gcc dot gnu dot org
2005-05-17 14:44 ` bonzini at gcc dot gnu dot org
2005-06-06 23:21 ` ro at gcc dot gnu dot org
2005-06-07 0:37 ` [Bug bootstrap/20155] [4.0 " gerald at pfeifer dot com
2005-07-08 1:37 ` mmitchel at gcc dot gnu dot org
2005-07-14 8:55 ` bonzini at gcc dot gnu dot org
2005-07-15 0:30 ` mark at codesourcery dot com [this message]
2005-08-08 17:01 ` bonzini at gcc dot gnu dot org
2005-08-08 17:03 ` aph at redhat dot com
2005-08-17 12:56 ` bonzini at gcc dot gnu dot org
2005-08-17 14:56 ` pinskia 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=20050715003051.28548.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: 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).