Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/google-breakpad: replace references to 'struct ucontext' with 'ucontext_t'
Date: Mon, 27 Nov 2017 11:05:28 +0100	[thread overview]
Message-ID: <87d144avfb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <04e7418d-735d-c9b3-3087-dbe78529cc48@mind.be> (Arnout Vandecappelle's message of "Thu, 23 Nov 2017 23:59:42 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 22-11-17 22:45, Thomas Petazzoni wrote:
 >> Hello,
 >> 
 >> Thanks for working on this topic!
 >> 
 >> On Wed, 22 Nov 2017 22:08:28 +0100, Romain Naour wrote:
 >>> Glibc change:
 >>> https://sourceware.org/git/?p=glibc.git;h=251287734e89a52da3db682a8241eb6bccc050c9
 >> 
 >> This commit log is very, very terse. Could you explain in more details
 >> what's going on?
 >> 
 >> Also, what is the effect if you use an older glibc version than 2.26 ?

 >  The ucontext_t type name is POSIX and has existed in glibc since 1997, in
 > uClibc and musl forever.

 >  I've extended the commit log with this and more explanation, and applied to
 > master, thanks.

Committed to 2017.02.x and 2017.08.x, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-11-27 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 21:08 [Buildroot] [PATCH] package/google-breakpad: replace references to 'struct ucontext' with 'ucontext_t' Romain Naour
2017-11-22 21:45 ` Thomas Petazzoni
2017-11-23 22:59   ` Arnout Vandecappelle
2017-11-27 10:05     ` Peter Korsgaard [this message]
2017-11-29 20:25     ` Romain Naour

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=87d144avfb.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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