public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paul Eggert <eggert@CS.UCLA.EDU>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8686: [sparc-solaris]3.2.1 multilib bootstrap fails: 32-bit Solaris 9 + Sun patch 112963-01
Date: Fri, 07 Mar 2003 08:29:00 -0000 [thread overview]
Message-ID: <20030307082607.3646.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/8686; it has been noted by GNATS.
From: Paul Eggert <eggert@CS.UCLA.EDU>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: bootstrap/8686: [sparc-solaris]3.2.1 multilib bootstrap fails: 32-bit Solaris 9 + Sun patch 112963-01
Date: 07 Mar 2003 00:19:02 -0800
bangerth@dealii.org writes:
> Paul, in your report you mention a patchset from Sun that was
> not available at the time. Did this situation change in the
> meantime?
Yes. The current patch revision is 112963-05, dated 2002-12-06
(available from <ftp://sunsolve.sun.com/pub/patches/112963-05.zip>).
If the workaround for Sun bug 4747851 is correct, this should
fix the problem. However, I haven't verified this, and also
the Sun database still lists the bug as not being fixed.
> I may not understand the problem in all details, but it
> appears to me that there is little value to have a bug
> report about a situation we cannot do anything about. The
> only thing I see is that we might want to document the
> problem in the target specific installation instructions.
Yes, that's what I'd do.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8686
next reply other threads:[~2003-03-07 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 8:29 Paul Eggert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-08 8:56 Paul Eggert
2003-03-07 15:06 Wolfgang Bangerth
2003-03-07 0:36 bangerth
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=20030307082607.3646.qmail@sources.redhat.com \
--to=eggert@cs.ucla.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).