From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22378 invoked by alias); 25 Aug 2009 20:19:50 -0000 Received: (qmail 22367 invoked by uid 22791); 25 Aug 2009 20:19:49 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mail2.impactweather.com (HELO mail2.impactweather.com) (209.249.14.182) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 25 Aug 2009 20:19:41 +0000 Received: (qmail 8774 invoked from network); 25 Aug 2009 20:19:26 -0000 Received: from chicago.impactweather.local (10.0.16.18) by mail2.impactweather.com with SMTP; 25 Aug 2009 20:19:26 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Build failure in libgfortran on i386-pc-solaris2.10 Date: Wed, 26 Aug 2009 09:11:00 -0000 Message-ID: In-Reply-To: References: <200907301438.n6UEcleh017505@impdell3.impactweather.local> From: "Arthur Haas" To: Cc: , "Tobias Burnus" Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-08/txt/msg00459.txt.bz2 =20 >> Art Haas writes: >> My bootstrap builds have been failing in the 'libgfortran' portion >> of the build since this patch: >>=20 >> 2009-07-27 Tobias Burnus >>=20 >> PR fortran/40863 >> * c99_functions.c: Define complex I, if not defined. >> Create prototypes for C99 functions to silence warnings. >> * gfortran.map: Add missing functions to GFORTRAN_C99_1.0 >> and new GFORTRAN_C99_1.1. >>=20 >> Here's the error message from the build log: >>=20 > [ ... snip error message ... ] > I've got the same problem on both Solaris 10/x86 and Solaris 11/SPARC (and > most likely, IRIX 6.5 will be affected, too). I've file PR > libfortran/41169 for the issue, assigned to Tobias. > It seems that the underlying issue is a problem in GCC's complex support on > Solaris 2, though. I've stopped building the fortran compiler for the moment. I haven't dug into what preprocessor trickery is needed to get this code to build just yet. I will keep an eye on the PR and be glad to test any potential patches offered. Art Haas