All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-11
Date: Wed, 12 Feb 2014 10:37:57 +0100	[thread overview]
Message-ID: <20140212103757.1f0431da@skate> (raw)
In-Reply-To: <CAKAx1cgjrtv9DxtETOTaR=BwpOGJ0A3HNVG+ciQGDbYh-serxg@mail.gmail.com>

Dear Lionel Orry,

On Wed, 12 Feb 2014 09:57:55 +0100, Lionel Orry wrote:
> Hi,
> 
> On Wed, Feb 12, 2014 at 8:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > <snip>
> >    powerpc |           enlightenment-0.17.3 | NOK | http://autobuild.buildroot.net/results/314694709b3a2d812c18acc70e374b3bc2fbedbd/
> 
> This is due to non-existent PTRACE_GETSIGINFO in sys/ptrace.h from
> used powerpc uclibc. I noticed this patch for v0.9.31:
> http://git.buildroot.net/buildroot/diff/?id=d8de970bae3744fe830e96a1ae0c4aff6ce47ba1
> I don't know which uclibc version is used, but more recent ones
> upstream do not include this fix, see for example
> http://git.uclibc.org/uClibc/tree/libc/sysdeps/linux/powerpc/sys/ptrace.h
> 
> I'm not sure about the right fix but it seems there's a problem with
> the provided sys/ptrace.h file for powerpc arch in uclibc. That's as
> far as I can go, I rarely use uclibc unfortunately.

The toolchain is using uClibc 0.9.33.2 + the uClibc patches that we had
back in the 2013.11-rc2 release.

We have a uclibc-0020-update-ptrace.h-to-latest-from-glibc.patch that
updates ptrace.h, but it seems like powerpc doesn't use the common
ptrace.h, but its own version, and this version hasn't been updated in
uClibc master.

Comparing the uClibc powerpc ptrace.h with the one in glibc indeed
shows a significant number of differences, including the addition of
PTRACE_SETSIGINFO. Someone should cook a patch that syncs up the
powerpc ptrace.h of uClibc with the one from glibc.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-02-12  9:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-11 Thomas Petazzoni
2014-02-12  8:32 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2014-02-12  9:21   ` Peter Korsgaard
2014-02-12  9:29     ` Thomas Petazzoni
2014-02-12  9:39       ` Peter Korsgaard
2014-02-12  9:45         ` Thomas Petazzoni
2014-02-12  9:52           ` Peter Korsgaard
2014-02-12 10:15             ` Thomas Petazzoni
2014-02-12  9:41   ` Thomas De Schampheleire
2014-02-12  9:47     ` Thomas Petazzoni
2014-02-12  9:50       ` Thomas De Schampheleire
2014-02-12 11:39         ` Thomas De Schampheleire
2014-02-12 12:29           ` Thomas De Schampheleire
2014-02-12 12:31             ` Thomas Petazzoni
2014-02-12 12:44               ` Thomas De Schampheleire
2014-02-12 12:47                 ` Thomas Petazzoni
2014-02-12 11:25   ` Samuel Martin
2014-02-12 17:52   ` Yann E. MORIN
2014-02-12  8:36 ` [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-11 Fabio Porcedda
2014-02-12  8:39   ` Thomas Petazzoni
2014-02-12  8:43     ` Fabio Porcedda
2014-02-12  8:57 ` Lionel Orry
2014-02-12  9:37   ` Thomas Petazzoni [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=20140212103757.1f0431da@skate \
    --to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.