From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/2] New internal function __access_noerrno
Date: Wed, 16 Nov 2016 18:29:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611161825560.26593@digraph.polyomino.org.uk> (raw)
In-Reply-To: <0139af69-4f6f-b524-5f33-a04e2d4e6bca@redhat.com>
On Wed, 16 Nov 2016, Carlos O'Donell wrote:
> Agreed, if we can't get building solutions for nacl and hurd then we can't
> test them. I've discussed this before without contributors and it's a serious
> issue for hurd that we really need to fix, but that is not your responsibility.
Now we have build-many-glibcs.py we could do with Hurd and NaCl people
either adding support for them (support for checking out and building
anything extra needed as equivalent of kernel headers, appropriate
configurations to build the toolchain for those systems) or providing
detailed instructions on how to build cross toolchains for them from
current upstream sources so someone else can add the support. (In the
Hurd case there may also be the issue of getting enough out-of-tree
changes into glibc so it actually builds and passes compilation tests with
unmodified glibc sources.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-16 18:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 17:04 [PATCH 1/2] Consolidate Linux access implementation Adhemerval Zanella
2016-11-10 17:04 ` [PATCH 2/2] New internal function __access_noerrno Adhemerval Zanella
2016-11-10 17:12 ` Andreas Schwab
2016-11-10 18:26 ` Adhemerval Zanella
2016-11-10 17:53 ` Siddhesh Poyarekar
2016-11-10 18:31 ` Adhemerval Zanella
2016-11-16 13:27 ` Adhemerval Zanella
2016-11-16 13:44 ` Adhemerval Zanella
2016-11-16 16:27 ` Carlos O'Donell
2016-11-16 18:29 ` Joseph Myers [this message]
2016-11-17 20:53 ` Kalle Olavi Niemitalo
2016-11-17 21:30 ` Adhemerval Zanella
2016-11-18 0:21 ` Kalle Olavi Niemitalo
2016-11-18 18:54 ` Adhemerval Zanella
2016-11-19 3:09 ` Siddhesh Poyarekar
2016-11-21 5:12 ` Kalle Olavi Niemitalo
2016-11-21 12:45 ` Adhemerval Zanella
2016-11-10 17:44 ` [PATCH 1/2] Consolidate Linux access implementation Siddhesh Poyarekar
2016-11-16 13:16 ` Carlos O'Donell
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.1611161825560.26593@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
/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).