From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Phil Edwards <pedwards@jaj.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry)
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.9909081830080.28804-100000@markab.dbai.tuwien.ac.at> (raw)
Message-ID: <19990930180200.X18hHzddD0d1F3V1nEb55_IPU9hVHPkGTQDm9PPVFhY@z> (raw)
In-Reply-To: <199908290224.WAA12572@jaj.com>
On Sat, 28 Aug 1999, Phil Edwards wrote:
>> 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. [...]
Please pester Sun as much as you can concerning their broken patches resp.
tools.
We have had quite high a number of problem reports after the release of
GCC 2.95.x, many (if not most) of which were due to broken Sun tools.
Perhaps someone could also provide a detailed description resp. an example
of the way Sun make is broken?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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
1999-09-08 9:33 ` Gerald Pfeifer [this message]
1999-09-30 18:02 ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry) Gerald Pfeifer
-- strict thread matches above, loose matches on Subject: below --
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-31 23:20 ` Gerald Pfeifer
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.9909081830080.28804-100000@markab.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=pedwards@jaj.com \
/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).