public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: "H.J. Lu" <hjl@lucon.org>
Cc: Russ Allbery <rra@stanford.edu>,
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry)
Date: Tue, 31 Aug 1999 23:20:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.10.9908301239370.18361-100000@markab.dbai.tuwien.ac.at> (raw)
Message-ID: <19990831232000.n0ejodVeeU0KS6IRKLWnaJHNlQwB_bRPcWXtDmpdUKY@z> (raw)
In-Reply-To: <19990829000659.7194E8EEE@ocean.lucon.org>

On Sat, 28 Aug 1999, H.J. Lu wrote:
> There are known bugs in binutils 2.9.1 on Solaris/Sparc. Quite a few
> Solaris/Sparc bugs have been fixed in binutils in cvs.

Thanks, HJ! I haved installed the patch below; it would be great if
someone would drop us a note once binutils have fixed these bugs in
an "official" release.

Gerald

Index: specific.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/install/specific.html,v
retrieving revision 1.45
diff -r1.45 specific.html
26a27
>   <li><a href="#sparc-sun-solaris*">sparc-sun-solaris*</a></li>
444a446,452
> <h3><a name="sparc-sun-solaris*">sparc-sun-solaris*</a></h3>
> 
> <p>binutils 2.9.1 has known bugs on this platform. We recommend to use the
> vendor tools (Sun as, Sun ld) until these have been fixed.</p>
> 
> 
> <hr>
501c509
< <p><i>Last modified on August 27, 1999.</i></p>
---
> <p><i>Last modified on August 30, 1999.</i></p>

  reply	other threads:[~1999-08-31 23:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.10.9908271827120.19328-100000@markab.dbai.tuwien.ac.at>
1999-08-27 15:28 ` Lost specific.html FAQ Entry Russ Allbery
1999-08-28  3:44   ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry) Gerald Pfeifer
1999-08-28 16:48     ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry) Russ Allbery
1999-08-28 17:07       ` H.J. Lu
1999-08-30  3:42         ` Gerald Pfeifer [this message]
1999-08-31 23:20           ` Gerald Pfeifer
1999-08-31 23:20         ` H.J. Lu
1999-08-30  2:51       ` Gerald Pfeifer
1999-08-30  3:08         ` Russ Allbery
1999-08-31 23:20           ` Russ Allbery
1999-08-31 23:20         ` Gerald Pfeifer
1999-08-30  9:29       ` Nick Ing-Simmons
1999-08-30 22:31         ` GCC 2.95.x: Major problems on Solaris Russ Allbery
1999-08-31 23:20           ` Russ Allbery
1999-08-31 23:20         ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry) Nick Ing-Simmons
1999-08-30  9:29       ` Nick Ing-Simmons
1999-08-31 23:20         ` Nick Ing-Simmons
1999-08-31 23:20       ` Russ Allbery
1999-08-29  6:57     ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQ Entry) Hans-Peter Nilsson
1999-08-31 23:20       ` Hans-Peter Nilsson
1999-08-31 23:20     ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry) Gerald Pfeifer
1999-08-31 23:20   ` Lost specific.html FAQ Entry Russ Allbery
1999-08-28 19:20 GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry) Phil Edwards
1999-08-31 23:20 ` Phil Edwards

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=Pine.GSO.4.10.9908301239370.18361-100000@markab.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.org \
    --cc=rra@stanford.edu \
    /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).