From: Khem Raj <raj.khem@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/7] eglibc: ptrace: protect ptrace_peeksiginfo_args from redefintion
Date: Mon, 26 Aug 2013 10:28:07 -0700 [thread overview]
Message-ID: <8DA5FFBA-9580-444A-AC2F-53C97EF6D105@gmail.com> (raw)
In-Reply-To: <CADkTA4Pit1BhOxw5C1gFobrj-m00CpS-n=WNtCkgdRdCDRymhg@mail.gmail.com>
On Aug 25, 2013, at 7:46 PM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> A final (maybe .. hopefully!?) thought on this. Do drop this change,
> but give me a
> few minutes to remove the offending structure from linux-libc-headers_3.10. That
> will also protect all users of yocto, regardless of the kernel unless
> they provide
> their own libc-headers .. and then they are on their own :)
>
> That leaves the c library alone, and should buy us time to fix the
> offending apps.
this is not again the correct place to fix it. since you will back this out say later
when all apps are fixed anyway. If we need to keep it I would rather have the app
builds failing and keep it enabled and it should not be the guy who is doing the kernel
headers upgrade to fix the whole ecosystem either. So add the headers by all means
and leave the old headers in there until the apps work correctly with new headers.
next prev parent reply other threads:[~2013-08-26 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 5:16 [v2 PATCH 0/7] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-25 5:16 ` [PATCH 1/7] kern-tools: usability, bug fixes and no guilt Bruce Ashfield
2013-08-25 5:16 ` [PATCH 2/7] guilt: update to latest git version Bruce Ashfield
2013-08-25 5:16 ` [PATCH 3/7] linux-libc-headers: update to v3.10 Bruce Ashfield
2013-08-25 5:16 ` [PATCH 4/7] eglibc: ptrace: protect ptrace_peeksiginfo_args from redefintion Bruce Ashfield
2013-08-25 6:35 ` Jonathan Liu
2013-08-25 14:22 ` Bruce Ashfield
2013-08-26 0:46 ` Khem Raj
2013-08-26 0:54 ` Bruce Ashfield
2013-08-26 2:14 ` Bruce Ashfield
2013-08-26 2:39 ` Bruce Ashfield
2013-08-26 2:46 ` Bruce Ashfield
2013-08-26 17:28 ` Khem Raj [this message]
2013-08-26 17:59 ` Bruce Ashfield
2013-08-26 21:16 ` Khem Raj
2013-08-26 21:27 ` Bruce Ashfield
2013-08-25 5:16 ` [PATCH 5/7] gst-plugins-good: fix 3.10 libc-headers build failure Bruce Ashfield
2013-08-25 6:36 ` Jonathan Liu
2013-08-25 14:20 ` Bruce Ashfield
2013-08-25 5:16 ` [PATCH 6/7] linux-yocto: introduce v3.10 Bruce Ashfield
2013-08-25 5:16 ` [PATCH 7/7] linux-yocto: remove 3.8 recipes Bruce Ashfield
2013-08-26 2:30 ` Saul Wold
2013-08-26 2:32 ` Bruce Ashfield
2013-08-26 4:10 ` Saul Wold
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=8DA5FFBA-9580-444A-AC2F-53C97EF6D105@gmail.com \
--to=raj.khem@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.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