From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: saul.wold@intel.com
Subject: Re: [PATCH 2/3] elfutils: upgrade to 0.158
Date: Wed, 28 May 2014 16:32:37 +0800 [thread overview]
Message-ID: <53859F25.3010905@windriver.com> (raw)
In-Reply-To: <9e30cf78bf731ad1eb0da5e84f86d87b09dc617f.1401265145.git.hongxu.jia@windriver.com>
On 05/28/2014 04:27 PM, Hongxu Jia wrote:
> Add 'm4-biarch.m4-tweak-AC_RUN_IFELSE-for-cross-compiling.patch' to fix cross compiling failure;
>
> Rebase 'elf_additions.diff' for 0.158;
I am sorry to missing
'm4-biarch.m4-tweak-AC_RUN_IFELSE-for-cross-compiling.patch'
and 'elf_additions.diff' in this patch.
V2 incoming.
//Hongxu
> Drop obsolete patches:
> - nm-Fix-size-passed-to-snprintf-for-invalid-sh_name-case.patch
> - elfutils-ar-c-fix-num-passed-to-memset.patch
> - fix-build-gcc-4.8.patch
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> .../{elfutils_0.155.bb => elfutils_0.158.bb} | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
> rename meta/recipes-devtools/elfutils/{elfutils_0.155.bb => elfutils_0.158.bb} (81%)
>
> diff --git a/meta/recipes-devtools/elfutils/elfutils_0.155.bb b/meta/recipes-devtools/elfutils/elfutils_0.158.bb
> similarity index 81%
> rename from meta/recipes-devtools/elfutils/elfutils_0.155.bb
> rename to meta/recipes-devtools/elfutils/elfutils_0.158.bb
> index b1f410c..c97be74 100644
> --- a/meta/recipes-devtools/elfutils/elfutils_0.155.bb
> +++ b/meta/recipes-devtools/elfutils/elfutils_0.158.bb
> @@ -7,23 +7,16 @@ DEPENDS = "libtool bzip2 zlib virtual/libintl"
>
> SRC_URI = "https://fedorahosted.org/releases/e/l/elfutils/${PV}/elfutils-${PV}.tar.bz2"
>
> -SRC_URI[md5sum] = "163a5712b86f6bdfebdf233cc6e2192d"
> -SRC_URI[sha256sum] = "68444a4526416ffd68852ec3c6a40ceddcca46538297322405319884c5d30ed8"
> +SRC_URI[md5sum] = "050a4909e452d01ab4747fd69d4036e0"
> +SRC_URI[sha256sum] = "be27af5c21352f53e010342bf1c68e0b9e18232dbf3adec7e2f9b41f6bbe397d"
>
> -SRC_URI += "\
> - file://redhat-portability.diff \
> - file://redhat-robustify.diff \
> - file://hppa_backend.diff \
> - file://arm_backend.diff \
> - file://mips_backend.diff \
> - file://m68k_backend.diff \
> - file://elf_additions.diff \
> - file://mempcpy.patch \
> +SRC_URI += " \
> + file://elf_additions.diff \
> + file://mempcpy.patch \
> file://dso-link-change.patch \
> - file://nm-Fix-size-passed-to-snprintf-for-invalid-sh_name-case.patch \
> - file://elfutils-ar-c-fix-num-passed-to-memset.patch \
> - file://fix-build-gcc-4.8.patch \
> + file://m4-biarch.m4-tweak-AC_RUN_IFELSE-for-cross-compiling.patch \
> "
> +
> # Only apply when building uclibc based target recipe
> SRC_URI_append_libc-uclibc = " file://uclibc-support.patch"
>
next prev parent reply other threads:[~2014-05-28 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 8:27 [PATCH 0/3] elfutils: upgrade to 0.158 Hongxu Jia
2014-05-28 8:27 ` [PATCH 1/3] elfutils: remove 0.155 Hongxu Jia
2014-05-28 8:27 ` [PATCH 2/3] elfutils: upgrade to 0.158 Hongxu Jia
2014-05-28 8:32 ` Hongxu Jia [this message]
2014-05-28 8:27 ` [PATCH 3/3] elfutils: backport from debian Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2014-05-28 8:49 [PATCH V2 0/3] elfutils: upgrade to 0.158 Hongxu Jia
2014-05-28 8:49 ` [PATCH 2/3] " Hongxu Jia
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=53859F25.3010905@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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