From: Nathan Sidwell <nathan@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: gnu on solaris
Date: Thu, 03 Oct 2002 13:47:00 -0000 [thread overview]
Message-ID: <3D9CA19B.70009@codesourcery.com> (raw)
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
next reply other threads:[~2002-10-03 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 13:47 Nathan Sidwell [this message]
2002-10-03 14:03 ` Gabriel Dos Reis
2002-10-03 14:48 ` Hans-Peter Nilsson
2002-10-03 16:55 ` Richard Henderson
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=3D9CA19B.70009@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.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).