public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Zack Weinberg <zackw@panix.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 05/10] Remove __need macros from errno.h (__need_Emath, __need_error_t).
Date: Thu, 11 May 2017 14:30:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1705111418380.4743@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAKCAbMiAHMgs0-pf1=ZEcPW0guoXH76s3i1u56ObnyPMBxmvgQ@mail.gmail.com>

On Thu, 11 May 2017, Zack Weinberg wrote:

> On Wed, May 10, 2017 at 8:03 AM, Florian Weimer <fweimer@redhat.com> wrote:
> > However, I still think that the NaCl port should be aligned with the rest of
> > glibc in this regard, and that Zack's cleanup should not introduce a new
> > extension point for it.  Particularly since we don't have a working port
> > right now which would exercise this functionality, so it's likely to be
> > broken anyway.
> 
> What would you have me do with sysdeps/nacl/errnos.awk, then?
> 
> (If the NaCl port doesn't work, should we just discard it altogether?
> I see value in keeping a non-Linux port around, but there are rumors
> to the effect that Google has abandoned NaCl[1] so maybe not _this_
> one...)

Well, we need such a port that works in current glibc sources (used 
together with upstream sources of other toolchain components), and where 
build-many-glibcs.py knows how and where to check out any OS-specific 
components (analogous to Linux kernel headers, for example) needed and how 
to build a cross toolchain for that target.  Neither NaCl nor Hurd meets 
those criteria at present; either could be made to meet them, if someone 
sufficiently familiar with building toolchains and glibc for that OS does 
the work required.

Otherwise, I'm not sure if anyone is currently working on the GNU/kFreeBSD 
port of glibc, but it's not upstream.  (And as a system with Unix-like 
syscalls, it would be less different from the Linux ports than NaCl or 
Hurd.)  And there's the WebAssembly port 
<https://github.com/pipcet/glibc>, also not (yet) upstream (neither is the 
GCC port, though at least some binutils support is upstream).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2017-05-11 14:30 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 15:41 [PATCH 00/10] All of my not-yet-reviewed patches Zack Weinberg
2017-05-09 15:41 ` [PATCH 09/10] Remove bits/string2.h Zack Weinberg
2017-05-09 15:41 ` [PATCH 02/10] Suppress internal declarations for most of the testsuite Zack Weinberg
2017-05-09 21:28   ` Joseph Myers
2017-05-10 11:56     ` Zack Weinberg
2017-05-12 15:40       ` H.J. Lu
2017-05-12 16:16         ` Zack Weinberg
2017-05-12 16:26           ` H.J. Lu
2017-05-15 14:18   ` [PATCH] Move tst-mutex*8* to tests-internal Tulio Magno Quites Machado Filho
2017-05-20 13:06     ` Zack Weinberg
2017-05-22 14:21       ` Stefan Liebler
2017-05-25 17:55         ` Tulio Magno Quites Machado Filho
2017-05-09 15:41 ` [PATCH 03/10] The bits/types/*.h treatment for stdio and wchar Zack Weinberg
2017-05-09 21:34   ` Joseph Myers
2017-05-10 11:52     ` Zack Weinberg
2017-05-20 21:05       ` Zack Weinberg
2017-05-22 14:56         ` Joseph Myers
2017-05-09 15:41 ` [PATCH 08/10] Don't install libio.h or _G_config.h Zack Weinberg
2017-05-09 15:41 ` [PATCH 04/10] Convert signal.h from __need macros to bits/types/ headers Zack Weinberg
2017-05-09 21:36   ` Joseph Myers
2017-05-17 17:41   ` Joseph Myers
2017-05-20 21:03     ` Zack Weinberg
2017-05-09 15:41 ` [PATCH 01/10] Remove _IO_MTSAFE_IO from public headers Zack Weinberg
2017-05-09 21:11   ` Joseph Myers
2017-05-09 15:41 ` [PATCH 07/10] Remove __need_IOV_MAX and __need_FOPEN_MAX Zack Weinberg
2017-05-09 15:56 ` [PATCH 10/10] Remove bits/string.h Zack Weinberg
2017-05-09 15:56 ` [PATCH 06/10] Remove __need_list_t and __need_res_state Zack Weinberg
2017-05-10  7:37   ` Florian Weimer
2017-05-20 19:37     ` Zack Weinberg
2017-05-09 15:56 ` [PATCH 05/10] Remove __need macros from errno.h (__need_Emath, __need_error_t) Zack Weinberg
2017-05-09 21:38   ` Joseph Myers
2017-05-10  7:31     ` Florian Weimer
2017-05-10 11:49       ` Joseph Myers
2017-05-10 12:03         ` Florian Weimer
2017-05-11 12:15           ` Zack Weinberg
2017-05-11 14:30             ` Joseph Myers [this message]
2017-05-11 14:46               ` Zack Weinberg
2017-05-11 14:53                 ` Florian Weimer
2017-05-11 14:48             ` Florian Weimer
2017-05-11 15:26               ` Joseph Myers
2017-05-11 15:42                 ` Andreas Schwab
2017-05-11 16:10                   ` Joseph Myers
2017-05-11 17:20                     ` Andreas Schwab
2017-05-11 16:19                   ` Florian Weimer
2017-05-11 17:25                     ` Andreas Schwab
2017-05-12  6:23                       ` Florian Weimer
2017-05-15  8:11                         ` Andreas Schwab
2017-05-15  8:13                           ` Florian Weimer
2017-05-15  8:24                             ` Andreas Schwab
2017-05-15  9:08                               ` Florian Weimer
2017-05-11  0:12 ` [PATCH 00/10] All of my not-yet-reviewed patches Joseph Myers

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=alpine.DEB.2.20.1705111418380.4743@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zackw@panix.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).