From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2428 invoked by alias); 23 Apr 2003 22:35:44 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 2414 invoked from network); 23 Apr 2003 22:35:44 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by sources.redhat.com with SMTP; 23 Apr 2003 22:35:44 -0000 Received: from localhost.localdomain (dhcp-172-16-25-221.sfbay.redhat.com [172.16.25.221]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id h3NMZdV26054; Wed, 23 Apr 2003 18:35:39 -0400 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h3NMYxYj006957; Wed, 23 Apr 2003 15:34:59 -0700 Received: (from aoliva@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h3NMYxda006953; Wed, 23 Apr 2003 15:34:59 -0700 To: Joe Buck Cc: Gabriel Dos Reis , Gerald Pfeifer , gcc@gcc.gnu.org, java@gcc.gnu.org, Eric Botcazou , "H. J. Lu" Subject: Re: 3.2.3-pre tarball 2: libjava build still fails on sparc-sun-solaris2.8 References: <20030417091616.A11341@synopsys.com> <20030417102820.A12714@lucon.org> <20030417144017.A1398@synopsys.com> <200304181447.51672.ebotcazou@libertysurf.fr> <20030423115153.A8351@synopsys.com> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Wed, 23 Apr 2003 23:35:00 -0000 In-Reply-To: <20030423115153.A8351@synopsys.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-04/txt/msg01198.txt.bz2 On Apr 23, 2003, Joe Buck wrote: > If the command that fails is libtool, and libtool has redirected the > error to /dev/null, and it's intermittent and unreproduceable, well, > I'm afraid that libtool will be considered guilty until proven innocent. In that case, indeed, it was libtool's fault. This was different, IMO, even though we can hopefully work around the issue in libtool as well. Sorry that I wasn't clear. And it was really meant as a joke. I hear all sorts of stuff about libtool all the time, and I've managed to not get offended or anything. It's just that it is such a complex piece of software that it's understandable that people prefer not to delve into it to figure out where exactly the problem is, and assume it's in libtool, which, unfortunately, is often true. > I realize that getting libtool to work right and portably is a tough job. Thanks; it is, indeed :-) -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer