Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kamil Rytarowski <n54@gmx.com>
To: Pedro Alves <palves@redhat.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Replicate src dir in build dir
Date: Wed, 04 Oct 2017 09:46:00 -0000	[thread overview]
Message-ID: <8491816b-1480-a470-d57f-024b639a6a48@gmx.com> (raw)
In-Reply-To: <f12f0b27-26f6-8d98-ac35-172fe478b945@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]

On 04.10.2017 00:04, Pedro Alves wrote:
> On 10/03/2017 09:16 PM, Kamil Rytarowski wrote:
>> On 03.10.2017 22:02, Pedro Alves wrote:
>>> On 09/29/2017 08:23 PM, Yao Qi wrote:
>>>> +
>>>> +case "${targ}" in
>>>> +*-*-freebsd* | *-*-kfreebsd*-gnu)
>>>> +	os_obs="fbsd-tdep.o solib-svr4.o";;
>>>> +*-*-netbsd* | *-*-knetbsd*-gnu)
>>>> +	os_obs="nbsd-tdep.o solib-svr4.o";;
>>>> +*-*-openbsd*)
>>>> +	os_obs="obsd-tdep.o solib-svr4.o";;
>>
>> There does not exist any GNU/kNetBSD distribution and nobody is doing
>> it. Please drop it.
> 
> Well, "does not exist" is a bit misleading, since there's
> https://www.debian.org/ports/netbsd/ .  (I had no idea about it,
> but google found it...)
> 

It was never finished and quickly abandoned. There was never a
functional GNU/kNetBSD distribution and nobody from the NetBSD community
aims for one.

There were other projects like reuse Gentoo portage on NetBSD, but this
does not replace the base distribution, just host the packaging tool on top.

> However, that page does say:
> 
>   This porting effort has long been abandoned. It has had no updates since october 2002.
>   The informations in this page are only for historical purposes. 
> 
> So it really sounds like we could zap it.  Ideally that should be a
> separate commit, with a gdb/NEWS entry change, and we'd drop
> it everywhere it's mentioned, not just configure.tgt.
> 
> "git grep knetbsd" finds hits in bfd and ld too, btw.
> 
> GCC dropped support last year, BTW:
> 
>   https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01370.html
> 
> which is another nail in the coffin...
> 

Right, I prompted to drop it in GCC and asked on a NetBSD mailing-list
whether someone is interested in such project - without volunteers.

> Thanks,
> Pedro Alves
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-10-04  9:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 14:42 Yao Qi
2017-09-19 20:44 ` Simon Marchi
2017-09-20  8:04   ` Yao Qi
2017-09-20  8:17     ` Simon Marchi
2017-09-20 14:26       ` Yao Qi
2017-09-20 11:26 ` Pedro Alves
2017-09-20 16:49   ` Yao Qi
2017-09-20 17:45     ` Pedro Alves
2017-09-29 19:23       ` Yao Qi
2017-10-03 20:02         ` Pedro Alves
2017-10-03 20:14           ` Kamil Rytarowski
2017-10-03 22:04             ` Pedro Alves
2017-10-04  9:46               ` Kamil Rytarowski [this message]
2017-10-06  9:29               ` Yao Qi
2017-10-04 11:41           ` Pedro Alves
2017-10-06 10:21           ` Yao Qi
2017-10-08  3:24 ` Tom Tromey
2017-10-08 21:04   ` Yao Qi
2017-10-11  1:25   ` Yao Qi
2017-10-11  3:26     ` Tom Tromey

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=8491816b-1480-a470-d57f-024b639a6a48@gmx.com \
    --to=n54@gmx.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.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