From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gdb@sourceware.org
Subject: Re: Solaris 11 buildbots
Date: Tue, 04 Sep 2018 21:42:00 -0000 [thread overview]
Message-ID: <ydd1sa9vt1l.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <2daf71d4-ae82-eebb-2a43-eee61f01819b@blastwave.org> (Dennis Clarke's message of "Tue, 4 Sep 2018 17:28:25 -0400")
Hi Dennis,
>> true, but I happen to have an S7 available for testing. I simply can't
>> afford buildbots for older Solaris 11 updates, especially given that
>> Solaris 11.3 support will end in the relatively near future.
>
> hrmmm .. yes, I still have S10 systems running on contract and I think
> 'support' will exist for a long long time. At least in the form of
> security updates. As for 11.4? Well I'll neet a Netra T4 it seems.
unfortunately not. As explained here
https://blogs.oracle.com/solaris/oracle-solaris-10-support-explained
https://blogs.oracle.com/solaris/solaris-10-extended-support-patches-patchsets-released
beyond January 2018 Solaris 10 support requires a special contract (that
we don't have). And even so, support will only last until 2021, at
which point at the very latest I'll stop supporting Solaris 10 in gcc
(and accordingly gdb).
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.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-09-04 21:42 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 [this message]
2018-09-04 22:07 ` Dennis Clarke
2018-09-05 8:03 ` Rainer Orth
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=ydd1sa9vt1l.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