Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris Webb <chris@arachsys.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Replace struct siginfo with siginfo_t
Date: Fri, 06 Jul 2012 13:10:00 -0000	[thread overview]
Message-ID: <20120706130952.GK13885@arachsys.com> (raw)
In-Reply-To: <4FF6E1B6.6020901@redhat.com>

Pedro Alves <palves@redhat.com> writes:

> On 07/06/2012 01:45 PM, Chris Webb wrote:
> > Glibc 2.16.0 removes the undocumented definition of 'struct siginfo' from
> > <bits/siginfo.h>. This struct is also available as the POSIX-defined
> > siginfo_t, so replace all uses of struct siginfo with siginfo_t.
> 
> Thanks, but this was already fixed by:
> 2012-03-21  Thomas Schwinge  <thomas@codesourcery.com>

Ah sorry, I should have checked git HEAD first. I think people will start
stumbling on this rather more frequently now the first 2.16.x glibc release
is out.

Best wishes,

Chris.


      reply	other threads:[~2012-07-06 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 12:45 Chris Webb
2012-07-06 13:02 ` Pedro Alves
2012-07-06 13:10   ` Chris Webb [this message]

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=20120706130952.GK13885@arachsys.com \
    --to=chris@arachsys.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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