public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: "H. J. Lu" <hjl@lucon.org>, gcc@gcc.gnu.org
Subject: Re: 3.2.3-pre tarball 2: libjava build still fails on sparc-sun-solaris2.8
Date: Mon, 21 Apr 2003 16:57:00 -0000	[thread overview]
Message-ID: <20030421085919.B5001@synopsys.com> (raw)
In-Reply-To: <200304190858.35822.ebotcazou@libertysurf.fr>; from ebotcazou@libertysurf.fr on Sat, Apr 19, 2003 at 08:59:48AM +0200

On Sat, Apr 19, 2003 at 08:59:48AM +0200, Eric Botcazou wrote:
> > I did another build and it worked; this time I tried setting both
> > SHELL and CONFIG_SHELL to /bin/ksh (previously I only had set
> > CONFIG_SHELL).  I still don't know why I got a failure, but there is
> > no error message because it is explicitly suppressed; I don't know
> > if it is an intermittent error but I can't make it happen again.
> 
> I never set SHELL and I've never run into a problem similar to yours. Weird.

I don't think it necessarily had an effect, might be an intermittent
bug; hard to tell when error messages are redirected to /dev/null.
 

  reply	other threads:[~2003-04-21 15:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 16:56 Joe Buck
2003-04-17 18:15 ` H. J. Lu
2003-04-17 22:16   ` Joe Buck
2003-04-18 16:26     ` Eric Botcazou
2003-04-18 17:18       ` Joe Buck
2003-04-18 17:25         ` Gabriel Dos Reis
2003-04-19  7:42         ` Eric Botcazou
2003-04-21 16:57           ` Joe Buck [this message]
2003-04-21  3:36       ` Gerald Pfeifer
2003-04-21 13:54         ` Gabriel Dos Reis
2003-04-23 19:03           ` Alexandre Oliva
2003-04-23 19:24             ` Joe Buck
2003-04-23 23:35               ` Alexandre Oliva
2003-04-24 16:15                 ` Michael S. Zick
2003-04-25 14:45             ` libjava build still fails on sparc-sun-solaris2.9 Gerald Pfeifer

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=20030421085919.B5001@synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=ebotcazou@libertysurf.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.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).