From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fan Xin <fan.xin@jp.fujitsu.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] elfutils: Upgrade 0.168 to 0.169
Date: Tue, 30 May 2017 08:37:11 +0100 [thread overview]
Message-ID: <1496129831.25229.153.camel@linuxfoundation.org> (raw)
In-Reply-To: <1495775169-24954-1-git-send-email-fan.xin@jp.fujitsu.com>
On Fri, 2017-05-26 at 14:06 +0900, Fan Xin wrote:
> 1) Upgrade elfutils from 0.168 to 0.169
> 2) Delete unnecessary patches which has been merged into 0.169
> 3) Rebase the patch files for 0.169
>
> Signed-off-by: Fan Xin <fan.xin@jp.fujitsu.com>
This fails to build for musl, the musl specific patch needs rebasing:
SRC_URI_append_libc-musl = " file://0001-build-Provide-alternatives-for-glibc-assumptions-hel.patch "
https://autobuilder.yocto.io/builders/nightly-musl/builds/277/steps/BuildImages/logs/stdio
Cheers,
Richard
prev parent reply other threads:[~2017-05-30 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 5:06 [PATCH] elfutils: Upgrade 0.168 to 0.169 Fan Xin
2017-05-26 14:30 ` Burton, Ross
2017-05-29 2:37 ` Fan Xin
2017-05-29 7:23 ` [PATCH v2] " Fan Xin
2017-05-30 7:37 ` 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=1496129831.25229.153.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fan.xin@jp.fujitsu.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 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.