From: "Joseph S. Myers" <joseph@codesourcery.com>
To: <ryan.arnold@gmail.com>
Cc: <libc-ports@sourceware.org>
Subject: Add ppca2 to ports powerpc/dl-procinfo
Date: Tue, 03 Jul 2012 17:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1207031702410.7079@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1207021128380.13316@digraph.polyomino.org.uk>
On Mon, 2 Jul 2012, Joseph S. Myers wrote:
> On Mon, 2 Jul 2012, Allan McRae wrote:
>
> > sysdeps/powerpc/dl-procinfo.c
> > sysdeps/powerpc/dl-procinfo.h
>
> I hadn't realised there were files in ports that would override
> corresponding files in libc when the repositories are merged (that is, if
> a configuration that previously didn't use ports now has the ports
> repository visible). It looks like it will be necessary to add ppca2
> support to the ports version to avoid any possible regressions - Ryan,
> does this (untested) patch look OK for the ports subdirectory immediately
> after the repository merge goes on master? (After the merge the powerpc
> maintainers should probably move at least the CPU support bits for powerpc
> in ports, if not the nofpu bits as well, directly into the libc sysdeps
> structure, but that's certainly a matter for the maintainers.)
I have applied this patch
<http://sourceware.org/ml/libc-alpha/2012-07/msg00010.html> to hopefully
reduce the risk of regressions for anyone newly getting powerpc ports
files where they didn't before. Please do fix things up if this patch has
in fact caused any problems of its own....
--
Joseph S. Myers
joseph@codesourcery.com
next parent reply other threads:[~2012-07-03 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.1207011326040.17026@digraph.polyomino.org.uk>
[not found] ` <4FF12517.1060601@archlinux.org>
[not found] ` <Pine.LNX.4.64.1207021128380.13316@digraph.polyomino.org.uk>
2012-07-03 17:05 ` Joseph S. Myers [this message]
2012-07-03 19:48 ` Ryan S. Arnold
[not found] ` <Pine.LNX.4.64.1207022358380.26474@digraph.polyomino.org.uk>
[not found] ` <20120703000257.279902C0DB@topped-with-meat.com>
[not found] ` <Pine.LNX.4.64.1207031326540.10948@digraph.polyomino.org.uk>
[not found] ` <20120703162337.A6E292C0D6@topped-with-meat.com>
[not found] ` <8739586a9i.fsf@schwinge.name>
2012-07-03 17:16 ` glibc-ports-merge branch available for testing Roland McGrath
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.1207031702410.7079@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=ryan.arnold@gmail.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).