Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
	Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gdb 7.11.1 -> 7.12
Date: Sat, 17 Dec 2016 09:45:58 +0000	[thread overview]
Message-ID: <1481967958.9843.28.camel@linuxfoundation.org> (raw)
In-Reply-To: <48DE1321-CAEA-4C5E-AAD5-6367729C3498@gmail.com>

On Fri, 2016-12-16 at 08:57 -0800, Khem Raj wrote:
> > 
> > On Dec 15, 2016, at 1:16 AM, Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.
> > com> wrote:
> > 
> > 1) Upgrade gdb from 7.11.1 to 7.12
> > 2) Delete 11 patches below, since they are integrated upstream.
> >    0001-include-sys-types.h-for-mode_t.patch
> >    0002-make-man-install-relative-to-DESTDIR.patch
> >    0003-mips-linux-nat-Define-_ABIO32-if-not-defined.patch
> >    0004-ppc-ptrace-Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch
> >    0005-Add-support-for-Renesas-SH-sh4-architecture.patch
> >    0006-Dont-disable-libreadline.a-when-using-disable-static.patch
> >    0007-use-asm-sgidefs.h.patch
> >    0008-Use-exorted-definitions-of-SIGRTMIN.patch
> >    0009-Change-order-of-CFLAGS.patch
> >    0010-resolve-restrict-keyword-conflict.patch
> >    0011-avx_mpx.patch
> I doubt if they all are merged. Can you check if you can build gdb
> for musl targets ?

Its confirmed as not building:

https://autobuilder.yocto.io/builders/nightly-musl/builds/104/steps/BuildImages/logs/stdio

Cheers,

Richard




      reply	other threads:[~2016-12-17  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  9:16 [PATCH] gdb 7.11.1 -> 7.12 Zheng Ruoqin
2016-12-15  9:50 ` Burton, Ross
2016-12-16 16:57 ` Khem Raj
2016-12-17  9:45   ` Richard Purdie [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=1481967958.9843.28.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=zhengrq.fnst@cn.fujitsu.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