From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gdb@sourceware.org
Subject: Re: Solaris 11 buildbots
Date: Wed, 05 Sep 2018 08:03:00 -0000 [thread overview]
Message-ID: <yddh8j4wf0q.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <edd6198c-6ac8-80ea-7077-c457439637b4@blastwave.org> (Dennis Clarke's message of "Tue, 4 Sep 2018 18:07:26 -0400")
Hi Dennis,
>> Support or no, dealing with Solaris 10 has often been only a nuisance in
>> recent gcc work; all the more reason to get rid of it in the not too
>> distant future.
>
> I have done reasonable builds of 8.1.0 but can't seem to find the
> motivation to look at anymore.
same here: I feel little inclination to debug bugs in a 5 (or 13
depending on how you count) years old OS release that are long fixed in
Solaris 11.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2018-09-05 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 19:43 Rainer Orth
2018-09-04 19:55 ` Dennis Clarke
2018-09-04 20:33 ` Rainer Orth
2018-09-04 21:28 ` Dennis Clarke
2018-09-04 21:42 ` Rainer Orth
2018-09-04 22:07 ` Dennis Clarke
2018-09-05 8:03 ` Rainer Orth [this message]
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=yddh8j4wf0q.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=dclarke@blastwave.org \
--cc=gdb@sourceware.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