public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@jaj.com>
To: gcc@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: <199908290224.WAA12572@jaj.com> (raw)
Message-ID: <19990831232000.l1sY5cePiZ9XSkP9L57HKOdAlfhROCzJ0Zh5r_Z5O3g@z> (raw)

>  1. I have already performed a couple of updates to
>     http://gcc.gnu.org/install/ but it seems we still need some
>     further ones.
>
>     Patches and hints are most welcome, as are updates to existing stuff.

Possibly remind the reader/installer that when installing the 5.0 tools,
the "install all the patches" script on that CD (which the CD install
instructions assume that you run, of course) adds 107058-01 automatically.
I only /happened/ to catch the patch # scrolling by and /happened/ to
recall reading the specific.html blurb a month before.  I suspect some
people can get into problems this way.


>  5. Has someone experiencing these problems already submitted bug reports
>     to the binutils developers resp. Sun?

I can submit bugs to Sun (we have a support contract and I have some spare
time), but I found out this week that the mailserver at work is on the ORBS
blacklist :-( so I've been holding off from joining the discussion until I
can actually send mail to these lists.  I will be more than willing to help
once I convince the mail admin...


Phil

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-28 19:20 Phil Edwards [this message]
1999-08-31 23:20 ` Phil Edwards
1999-09-08  9:33 ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry) Gerald Pfeifer
1999-09-30 18:02   ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
1999-08-28  3:44 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
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-31 23:20     ` 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

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=199908290224.WAA12572@jaj.com \
    --to=pedwards@jaj.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).