From: "Carlos O'Donell" <carlos@redhat.com>
To: GNU C Library <libc-alpha@sourceware.org>,
"libc-ports@sourceware.org" <libc-ports@sourceware.org>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: The hppa port is now moved out of ports.
Date: Tue, 29 Apr 2014 08:20:00 -0000 [thread overview]
Message-ID: <535F60AC.4050702@redhat.com> (raw)
Joseph,
The hppa port is now in libc.
The disassembly of the shared libraries appears identical.
The hppa port doesn't depend on any other ports ports
so no #includes needed adjusting.
The hppa port uses the preferred sysdeps/unix/sysv/linux/hppa/nptl.
The move ChangeLog entry was added to the top-level ChangeLog
indicating that hppa now uses that top-level ChangeLog.
There are no more ports left in ports.
Is there any other next step (other than fixing
up more of the hppa port)?
Cheers,
Carlos.
next reply other threads:[~2014-04-29 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 8:20 Carlos O'Donell [this message]
2014-04-29 15:21 ` Joseph S. Myers
2014-04-29 21:29 ` Carlos O'Donell
2014-04-29 21:46 ` Joseph S. Myers
2014-04-29 21:58 ` Carlos O'Donell
2014-04-29 22:07 ` Joseph S. Myers
2014-04-29 22:35 ` Carlos O'Donell
2014-04-30 17:44 ` Roland McGrath
2014-04-30 17:46 ` 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=535F60AC.4050702@redhat.com \
--to=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@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).