From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2358 invoked by alias); 22 Mar 2004 14:12:19 -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 2337 invoked from network); 22 Mar 2004 14:12:13 -0000 Received: from unknown (HELO mail.Mi8.com) (63.240.6.41) by sources.redhat.com with SMTP; 22 Mar 2004 14:12:13 -0000 Received: from 172.16.1.69 by mail.Mi8.com with ESMTP (- GW05 Welcome to Mi8 Corporation www.Mi8.com); Mon, 22 Mar 2004 09:12:04 -0500 X-Server-Uuid: 1970C553-821F-4189-A6A2-1AA80FC3CCA8 Received: from MI8NYCMAIL02.Mi8.com ([172.16.1.23]) by nycexsmtp01.Mi8.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 22 Mar 2004 09:12:04 -0500 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: GCC 3.2.3 on Solaris 2.7 Date: Mon, 22 Mar 2004 17:04:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Balaji Srinivasa" To: "Eric Botcazou" cc: gcc@gcc.gnu.org X-OriginalArrivalTime: 22 Mar 2004 14:12:04.0137 (UTC) FILETIME=[A6C3F990:01C41017] X-WSS-ID: 6C402BBE1FG11722823-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-SW-Source: 2004-03/txt/msg01298.txt.bz2 >=20 > > 4. I built Python 2.1 for a 32 bit sample > > 5. I built lsof 4.70 for a 64 bit sample > > 6. They both built successfully and ran successfully. >=20 > Nice! >=20 > > I am thinking that these failures might be due to > > (a) me setting --disable-libgcj > > (b) me setting --enable-languages=3Dc,c++,objc > > and the building of the sparcv9 dirs. >=20 > No, I don't think so, these are common and well-tested=20 > options. I'd tend to=20 > think of a shell problem if you used /bin/sh, such problems are very=20 > frequent on Solaris. >=20 > > This did not happen on 2 other 32 bit builds. > > 1. Solaris 2.6 > > 2. Linux 2.4 >=20 > Sure, sparc-sun-solaris2.6 is not multilibed. I think the shell was the problem. In fact, the documentation should state that CONFIG_SHELL should always be exported, or, configure should take the SHELL value from the env. After that was set, a complete rebuild was successful. However, config.status still shows #!/bin/sh whatever is set. thx to Eric, balaji