public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	GNU C Library <libc-alpha@sourceware.org>,
		libc-ports@sourceware.org,
	Adhemerval Zanella <azanella@linux.vnet.ibm.com>
Subject: Re: RFA: Port maintainers: Convert WORDSIZE[32|64]/ld to abi-variants
Date: Wed, 30 May 2012 13:00:00 -0000	[thread overview]
Message-ID: <CAMe9rOqOQDjKDq7RUg8CN-rfD7bgBm_SH0rK7XDCs2+zcX3uYw@mail.gmail.com> (raw)
In-Reply-To: <4FC5DF01.3090308@linux.vnet.ibm.com>

On Wed, May 30, 2012 at 1:49 AM, Andreas Krebbel
<krebbel@linux.vnet.ibm.com> wrote:
> On 05/30/2012 02:29 AM, H.J. Lu wrote:
>> On Sat, May 26, 2012 at 12:22 PM, Joseph S. Myers
>> <joseph@codesourcery.com> wrote:
>>> On Sat, 26 May 2012, H.J. Lu wrote:
>>>
>>>> I restored sh and sparc entries in shlib-versions on hjl/abi branch.
>>>> The new patch is at
>>>>
>>>> http://sourceware.org/git/?p=glibc.git;a=patch;h=0d1f492b3cf83a200601c1f49734b048c5547e57
>>>
>>> Provided the new version passes architecture maintainer testing I think it
>>> will probably be OK for 2.16, given the comments Roland requested saying
>>> that the use of soname variables set in makefiles is wrong and a bug filed
>>> with a 2.17 milestone to get this cleaned up properly along the lines I
>>> proposed (naming ABI variants, not triplets, in shlib-versions, with all
>>> the architecture information in shlib-versions moving to appropriate
>>> sysdeps directories shared by all the ABI variants of each architecture).
>>>
>>
>> I rebased hjl/abi branch.  Has anyone verified it on sparc, powerpc an s390x?
>
> I've tested your patch on s390 and s390x. No regressions.
>
> Bye,
>
> -Andreas-
>

Adhemerval,

Can you test hjl/abi branch on powerpc?

Thanks.


-- 
H.J.

  reply	other threads:[~2012-05-30 13:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 13:37 H.J. Lu
2012-05-26 17:03 ` Joseph S. Myers
2012-05-26 17:51   ` H.J. Lu
2012-05-26 19:22     ` Joseph S. Myers
2012-05-26 20:42       ` H.J. Lu
2012-05-30  0:29       ` H.J. Lu
2012-05-30  0:39         ` David Miller
2012-05-30  3:15           ` David Miller
2012-05-30  3:27             ` H.J. Lu
2012-05-30  8:49         ` Andreas Krebbel
2012-05-30 13:00           ` H.J. Lu [this message]
2012-05-31 15:17         ` Joseph S. Myers
2012-05-31 15:32           ` H.J. Lu
2012-06-01 14:06             ` Joseph S. Myers
2012-06-01 14:21               ` H.J. Lu
2012-06-01 15:07                 ` Joseph S. Myers
2012-06-01 15:27                   ` H.J. Lu
2012-06-01 20:16                     ` Joseph S. Myers
2012-06-01 20:32                       ` Roland McGrath
2012-05-30 18:58   ` Thomas Schwinge
2012-05-30 19:00     ` H.J. Lu

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=CAMe9rOqOQDjKDq7RUg8CN-rfD7bgBm_SH0rK7XDCs2+zcX3uYw@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=azanella@linux.vnet.ibm.com \
    --cc=joseph@codesourcery.com \
    --cc=krebbel@linux.vnet.ibm.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).