public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: libc-ports@sourceware.org, GNU C Library <libc-alpha@sourceware.org>
Subject: RFC: Please check if your glibc port defines __WORDSIZE_COMPAT32
Date: Sat, 19 May 2012 13:58:00 -0000	[thread overview]
Message-ID: <CAMe9rOpjgsvitQvYveyZCtWW=fvXTVtj9rCRex7L5EEPRaSn4w@mail.gmail.com> (raw)

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.

             reply	other threads:[~2012-05-19 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19 13:58 H.J. Lu [this message]
2012-05-21 20:51 ` 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='CAMe9rOpjgsvitQvYveyZCtWW=fvXTVtj9rCRex7L5EEPRaSn4w@mail.gmail.com' \
    --to=hjl.tools@gmail.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).