From: "Joseph S. Myers" <joseph@codesourcery.com>
To: <libc-ports@sourceware.org>
Cc: Richard Henderson <rth@redhat.com>,
Chris Metcalf <cmetcalf@tilera.com>,
Carlos O'Donell <carlos@redhat.com>
Subject: Ordering of ports move to libc
Date: Thu, 30 Jan 2014 18:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1401301814160.7025@digraph.polyomino.org.uk> (raw)
After 2.19 has branched and master reopened for 2.20 development, we would
like to move ports architectures to libc, as described at
<https://sourceware.org/ml/libc-alpha/2014-01/msg00373.html> (which
includes the architecture maintainers doing the moves for their
architectures and checking that the before-and-after disassembly of
installed shared libraries is identical).
I've checked what cases there are where one ports architecture uses files
from another. In such cases, either the moves need to be
dependency-ordered, or else the #include direction needs to be reversed at
move time. To avoid unnecessary churn and potential conflicts when two
people try to move their architectures at once, I suggest
dependency-ordering if the depended-on architecture can be moved quickly.
The following architectures use linux-generic (both via Implies files and
#include): aarch64, tile. So I suggest that linux-generic is moved early.
There are the following other dependencies (for example, arm uses files
from alpha):
aarch64: arm
arm: alpha
microblaze: alpha
mips: alpha arm hppa
Thus, I suggest moving alpha early - and once that's moved, I'll move arm.
hppa is blocked by not building rather than by dependencies; I'll reverse
the #include direction between sysdeps/unix/sysv/linux/hppa/umount.c and
sysdeps/unix/sysv/linux/mips/mips64/umount.c unless hppa is fixed soon
(fixing the hppa build would unblock it for move to libc).
As well as alpha, ia64 and m68k are unblocked for moving as soon as master
reopens, and tile is unblocked as soon as linux-generic has moved (or they
could move at the same time). I intend to remove am33 as soon as master
reopens.
When moving a port, as well as moving the files you should properly update
the lists of ports in the libc README file as well.
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2014-01-30 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 18:29 Joseph S. Myers [this message]
2014-01-30 19:42 ` Chris Metcalf
2014-01-30 21:07 ` Roland McGrath
2014-01-30 21:29 ` Joseph S. Myers
2014-01-30 21:31 ` Roland McGrath
2014-01-31 14:58 ` Richard Henderson
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=Pine.LNX.4.64.1401301814160.7025@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=cmetcalf@tilera.com \
--cc=libc-ports@sourceware.org \
--cc=rth@redhat.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).