This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.0.3 + binutils 2.11.2 problems on sparc-sun-solaris2.6
- From: Paul Eggert <eggert at twinsun dot com>
- To: chowell at redhat dot com
- Cc: gcc-bugs at gcc dot gnu dot org, bug-binutils at gnu dot org, aoliva at redhat dot com, dj at redhat dot com
- Date: Tue, 5 Feb 2002 01:46:43 -0800 (PST)
- Subject: Re: gcc 3.0.3 + binutils 2.11.2 problems on sparc-sun-solaris2.6
- References: <200202050834.AAA27559@southpole.cygnus.com>
> From: Colin Howell <chowell@redhat.com>
> Date: Tue, 5 Feb 2002 00:34:47 -0800 (PST)
>
> I do not know if Sun has ever provided a fix for this bug for Solaris
> 2.6.
They haven't announced a fix, as far as I know.
gcc-3.0.3/gcc/doc/install.texi contains a discussion of this problem
for Solaris 7, along with workarounds. Perhaps you can use that
discussion as a source of ideas for similar workarounds for Solaris
2.6. (For example, Sun patch 107733-09 might help. This patch is
available to everyone.)
> Nor do I have the ability to patch any Solaris machine that I
> have access to.
If you're on an ancient unpatched Solaris 2.6 box, there are lots of
ways to become root. People really ought to install the recommended
patches, regardless of the GCC problems. (I know they don't always do
it....)
> Is there any way to work around this problem, or at least warn Solaris
> 2.6 users not to configure gcc 3.0.4 to use binutils 2.11.2, before
> gcc 3.0.4 goes out?
Surely install.texi could be changed to warn about the problem.
But I'm afraid you'll have to write the doc patch, as I rarely use
Solaris 2.6 these days.