public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
* RFC: Please check if your glibc port defines __WORDSIZE_COMPAT32
@ 2012-05-19 13:58 H.J. Lu
  2012-05-21 20:51 ` H.J. Lu
  0 siblings, 1 reply; 2+ messages in thread
From: H.J. Lu @ 2012-05-19 13:58 UTC (permalink / raw)
  To: libc-ports, GNU C Library

Hi Glibc port maintainers,

I will check in a patch on Monday, May 21, 2012 to rename
__WORDSIZE_COMPAT32 to __WORDSIZE_TIME64_COMPAT32:

http://sourceware.org/ml/libc-alpha/2012-05/msg01355.html

If your port defines __WORDSIZE_COMPAT32, you need to rename
it to __WORDSIZE_TIME64_COMPAT32 after my patch is
checked in.

Thanks.


-- 
H.J.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RFC: Please check if your glibc port defines __WORDSIZE_COMPAT32
  2012-05-19 13:58 RFC: Please check if your glibc port defines __WORDSIZE_COMPAT32 H.J. Lu
@ 2012-05-21 20:51 ` H.J. Lu
  0 siblings, 0 replies; 2+ messages in thread
From: H.J. Lu @ 2012-05-21 20:51 UTC (permalink / raw)
  To: libc-ports, GNU C Library

On Sat, May 19, 2012 at 6:58 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> Hi Glibc port maintainers,
>
> I will check in a patch on Monday, May 21, 2012 to rename
> __WORDSIZE_COMPAT32 to __WORDSIZE_TIME64_COMPAT32:
>
> http://sourceware.org/ml/libc-alpha/2012-05/msg01355.html
>
> If your port defines __WORDSIZE_COMPAT32, you need to rename
> it to __WORDSIZE_TIME64_COMPAT32 after my patch is
> checked in.
>

The patch has been checked into master branch.

-- 
H.J.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-05-21 20:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-19 13:58 RFC: Please check if your glibc port defines __WORDSIZE_COMPAT32 H.J. Lu
2012-05-21 20:51 ` H.J. Lu

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).