From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation]
Date: Thu, 21 Sep 2017 14:31:00 -0000 [thread overview]
Message-ID: <yddk20sp1i5.fsf_-_@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <yddtvzwp293.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Thu, 21 Sep 2017 16:14:48 +0200")
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> However, this section is only needed on Solaris < 10, which is why I
> didn't notice it until I tried an i386-pc-solaris2.9 build. It's
> probably time to remove support for those old Solaris versions in gdb,
> too: gcc lost them after 4.9.
I'm pretty certain we should: the Solaris 9/x86 build didn't complete,
even with the configure.nat section fixed:
In file included from build-gnulib/import/wchar.h:87:0,
from /vol/gcc-4.9/include/c++/4.9.0/cwchar:44,
from /vol/gcc-4.9/include/c++/4.9.0/bits/postypes.h:40,
from /vol/gcc-4.9/include/c++/4.9.0/bits/char_traits.h:40,
from /vol/gcc-4.9/include/c++/4.9.0/string:40,
from /vol/src/gnu/gdb/gdb/local/gdb/common/common-utils.h:23,
from /vol/src/gnu/gdb/gdb/local/gdb/common/common-defs.h:78,
from /vol/src/gnu/gdb/gdb/local/gdb/defs.h:28,
from /vol/src/gnu/gdb/gdb/local/gdb/gdb.c:19:
/vol/gcc-4.9/lib/gcc/i386-pc-solaris2.9/4.9.0/include-fixed/wchar.h:59:12: error: ‘std::wcstok’ has not been declared
using std::wcstok;
^
/vol/gcc-4.9/lib/gcc/i386-pc-solaris2.9/4.9.0/include-fixed/wchar.h:60:12: error: ‘std::wcsftime’ has not been declared
using std::wcsftime;
^
This bad interaction between gnulib and fixed Solaris 9 headers may be
fixable, but even trying to seems like a total waste of time.
How is obsoletion/removal handled in gdb? In gcc, in one release a
target is obsoleted and trying to build it yields an error which can be
overridden with --enable-obsolete. Unless someone steps up to continue
maintenance, the code is removed in the next release.
Does gdb go for immediate removal instead? I have no idea which release
last built/worked on Solaris 9. I have a build of 7.11 lying around,
but never tried anything later.
Thoughts?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2017-09-21 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 13:02 Fix gdb 8.1 Solaris compilation Rainer Orth
2017-09-21 13:17 ` Andreas Schwab
2017-09-21 14:14 ` Rainer Orth
2017-09-21 14:31 ` Rainer Orth [this message]
2017-09-21 14:39 ` Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation] Pedro Alves
2017-09-22 14:45 ` Rainer Orth
2017-09-22 15:40 ` Pedro Alves
2017-09-26 11:20 ` Rainer Orth
2017-09-26 11:26 ` Pedro Alves
2017-09-26 13:25 ` Rainer Orth
2017-09-26 13:45 ` Pedro Alves
2017-09-26 13:55 ` Rainer Orth
2017-09-26 14:18 ` Pedro Alves
2017-09-26 14:21 ` Pedro Alves
2017-10-03 13:01 ` Rainer Orth
2017-09-29 11:53 ` Eli Zaretskii
2017-09-21 14:21 ` Fix gdb 8.1 Solaris compilation Pedro Alves
2017-09-21 14:23 ` 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=yddk20sp1i5.fsf_-_@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
/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