From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation]
Date: Tue, 26 Sep 2017 11:26:00 -0000 [thread overview]
Message-ID: <bf72bd45-4f76-aaeb-7160-be41b6f04186@redhat.com> (raw)
In-Reply-To: <ydd7ewlwvtm.fsf@CeBiTec.Uni-Bielefeld.DE>
>> I mildly wonder if the adding of sol-thread.o could move
>> from gdb/configure.ac to gdb/configure.nat.
>
> Certainly: no point hiding a static addition in configure.ac. I've also
> found that the remaining code in the solaris* section there can go, too:
>
> * Since Solaris 10, dlopen has moved to libc and libdl.so is just a
> filter on ld.so.1, so no need to check.
>
> * $RDYNAMIC is already handled above (and is a no-op with Solaris ld
> anyway).
>
Great!
> The attached revised patch has been tested on sparcv9-sun-solaris2.10,
> sparcv9-sun-solaris2.11.4 (with
> https://sourceware.org/ml/gdb-patches/2017-09/msg00787.html applied so
> mainline compiles on Solaris/SPARC at all), amd64-pc-solaris2.10,
> amd64-pc-solaris2.11.4, and x86_64-pc-linux-gnu.
>
> I've also started an i386-pc-solaris2.9 build to check that it really
> stops as expected.
>
> Testing is very weird, though: Linux/x86_64 only shows a few failures,
> but Solaris is a mess: on Solaris 10, the vast majority of tests time
> out (although gdb seems to work reasonably well interactively), while
> many more work on Solaris 11.4 until testing runs into what seems an
> infinite loop of
>
> FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=main: mi=main: force-fail=1: run failure detected (timeout)
>
> Nonetheless, ok for mainline now?
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-09-26 11:26 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 ` Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation] Rainer Orth
2017-09-21 14:39 ` 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 [this message]
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=bf72bd45-4f76-aaeb-7160-be41b6f04186@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.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