From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: Removing the glibc NaCl port
Date: Thu, 13 Apr 2017 18:11:00 -0000 [thread overview]
Message-ID: <0a4e39b6-d724-4c06-c987-0b742fc123b5@redhat.com> (raw)
In-Reply-To: <36f50cc7-ec80-9c38-9c52-f4dbb52290c0@linaro.org>
On 04/13/2017 07:44 PM, Adhemerval Zanella wrote:
>
>
> On 13/04/2017 12:45, Florian Weimer wrote:
>> I just realized that my pipe2 removal probably breaks the NaCl port.
>>
>> Can we remove it? It blocks useful cleanups which are compatible with the out-of-tree Hurd port.
>>
>> I don't think anyone has ever reported test results for release builds. scripts/build-many-glibcs.py lacks support for it, so we don't even know if it still builds.
>>
>> I hope this proposal is not too controversial.
> Also last time I check from official documentation [1], it uses ancient
> version without any documentation to actually build/check glibc on it.
> I have the impression it is bit-rotten for some time.
>
> If the idea is to keep supporting, I think we need at least proper
> documentation on how to actually build and tests, preferable with
> build-many-glibc.py support.
>
> [1] https://developer.chrome.com/native-client/sdk/download
There is a Git repository with a NaCl port to GCC 4.9, it seems:
https://chromium.googlesource.com/native_client/nacl-gcc/+/ng/4.9/master
Version-wise, this is sufficient to build glibc (unlike the
GCC-4.4-derived version in Fedora). I have not checked if it actually
works. GCC upstream no longer supports any of the 4.x branches, so this
is a dead end anyway.
The NaCl SDK seems to have switched to Clang/LLVM, and therefore cannot
build glibc anymore. (I checked the pepper_56 bundle.)
Thanks,
Florian
prev parent reply other threads:[~2017-04-13 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 15:45 Florian Weimer
2017-04-13 17:44 ` Adhemerval Zanella
2017-04-13 18:11 ` Florian Weimer [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=0a4e39b6-d724-4c06-c987-0b742fc123b5@redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).