From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27034 invoked by alias); 3 Oct 2002 19:59:26 -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 27023 invoked from network); 3 Oct 2002 19:59:26 -0000 Received: from unknown (HELO uha.cs.bris.ac.uk) (62.30.75.143) by sources.redhat.com with SMTP; 3 Oct 2002 19:59:26 -0000 Received: from codesourcery.com (localhost.localdomain [127.0.0.1]) by uha.cs.bris.ac.uk (8.11.6/8.11.6) with ESMTP id g93JxO305063; Thu, 3 Oct 2002 20:59:24 +0100 Message-ID: <3D9CA19B.70009@codesourcery.com> Date: Thu, 03 Oct 2002 13:47:00 -0000 From: Nathan Sidwell Organization: Codesourcery LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gcc@gcc.gnu.org Subject: gnu on solaris Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-10/txt/msg00182.txt.bz2 Hi, Unless I'm building things stupidly, current gnu tools seem awkward &| unusable on sparc-solaris. This is a convergence of binutils/gcc/gdb issues, and I'd like to check that it's not just me, I tested this on sparc-sun-solaris2.8 1) binutils 2.13 can't build shared objects - well, it builds them but they segfault. This manifested as an immediate segfault in c++ programs compiled by a subsequently built g++. binutils tests passed (IIRC). This took a little tracking, and of course the obvious suspect (the new compiler) was innocent. 2) config & building required CONFIG_SHELL=/bin/bash SHELL=/bin/bash ../gcc/configure ... make CONFIG_SHELL=/bin/bash SHELL=/bin/bash bootstrap without telling make, the build forgets partway through that I said use bash, not sh, and went back to using /bin/sh in a place where it fails. 3) gdb 5.2 & 5.2.1 couldn't read some 3.3pre core files. this seemed a bit flakey, but on a 3.2 generated core, gdb went into some kind of infinite loop requiring a kill -9. gdb 5.0 was ok, but has problems with C++ structures (it thinks many of them are incomplete) the current install.texi file does not document these issues. nathan -- Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC 'But that's a lie.' - 'Yes it is. What's your point?' nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org