public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Rical Jasan <ricaljasan@pacific.net>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] Remove the bulk of the NaCl port.
Date: Sat, 27 May 2017 15:20:00 -0000	[thread overview]
Message-ID: <CAKCAbMgpiGkOgJ=hOiU++ZMz3a9dUDCmE_3eU57xrVv9mEZdyg@mail.gmail.com> (raw)
In-Reply-To: <e16ed037-d939-7e3b-d2a4-842bff0515e4@pacific.net>

On Sat, May 27, 2017 at 6:08 AM, Rical Jasan <ricaljasan@pacific.net> wrote:
> On 05/11/2017 05:37 PM, Zack Weinberg wrote:
>> The NaCl port has not been actively maintained since before the 2.25
>> release.  The complementary GCC back-end was never contributed to GCC,
>> and we are given to understand that the current NaCl SDK has switched
>> to Clang and therefore cannot be used to build glibc anymore, so we
>> doubt that the port remains useful.
>
> FYI, the wiki home page (at least) still references this port.  Very
> bottom of the page; https://sourceware.org/glibc/wiki/

... and it links to a dead website.  I've removed it.

zw

      reply	other threads:[~2017-05-27 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  0:38 Zack Weinberg
2017-05-12  0:38 ` [PATCH 2/2] Remove vestiges of NaCl port from ARM assembly files Zack Weinberg
2017-05-12  8:22   ` Florian Weimer
2017-05-12 14:09     ` Joseph Myers
2017-05-12 14:30       ` Zack Weinberg
2017-05-20 12:15         ` Zack Weinberg
2017-05-12 15:01       ` Florian Weimer
2017-05-20 21:39       ` Matt Turner
2017-05-22 14:54         ` Joseph Myers
2017-05-12  6:21 ` [PATCH 1/2] Remove the bulk of the NaCl port Florian Weimer
2017-05-27 10:08 ` Rical Jasan
2017-05-27 15:20   ` Zack Weinberg [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='CAKCAbMgpiGkOgJ=hOiU++ZMz3a9dUDCmE_3eU57xrVv9mEZdyg@mail.gmail.com' \
    --to=zackw@panix.com \
    --cc=libc-alpha@sourceware.org \
    --cc=ricaljasan@pacific.net \
    /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).