public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: coypu@sdf.org
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Use a specfile that actually allows building programs on NetBSD
Date: Thu, 29 Jun 2017 23:49:00 -0000	[thread overview]
Message-ID: <20170629234853.GB25819@SDF.ORG> (raw)
In-Reply-To: <e38f339b-0180-833b-8fb3-f4c1a677c4ed@redhat.com>

On Thu, Jun 29, 2017 at 05:23:37PM -0600, Jeff Law wrote:
> On 06/29/2017 09:51 AM, coypu wrote:
> > I was thinking of holding a party for the upcoming one year anniversary
> > of pinging this patch, that was committed to NetBSD's copy of GCC about
> > a decade ago. without it, I can't compile simple programs.
> When it was committed to NetBSD isn't at all relevant.  We don't scour
> downstream uses for patches that might be useful and since few, if any,
> of the most active GCC developers use NetBSD we're unlikely to trip over
> the problem ourselves.  That makes us reliant upon others to report bugs
> and sometimes to even provide patches to fix platform specific issues.
> 
> Krister indicated back when you first posted the patch in Jan that he
> was going to fix this and other issues in specs handling, but I don't
> see that Krister ever followed up.
> 
> I wouldn't at all be surprised if this needs further work for pthreads.
> But I'll have to leave investigation there to folks that use NetBSD.
> 
> I've installed your patch on the trunk.

Thank you.

I've spoken with Krister and he is responsive and still interested in
cleaning everything up, but it's good to have things working until then.

I've mentioned it as I'd like to close N many years of not upstreaming
patches :-) sometimes we have good changes, too, but they'll be mostly
netbsd ones.

      reply	other threads:[~2017-06-29 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 15:51 coypu
2017-06-29 16:05 ` Joseph Myers
2017-06-29 23:23 ` Jeff Law
2017-06-29 23:49   ` coypu [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=20170629234853.GB25819@SDF.ORG \
    --to=coypu@sdf.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).