public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: Khem Raj <raj.khem@gmail.com>, "Maxin B. John" <maxin.john@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/9] elfutils: 0.163 -> 0.164
Date: Thu, 21 Jan 2016 11:23:41 +0800	[thread overview]
Message-ID: <56A04F3D.8000902@windriver.com> (raw)
In-Reply-To: <EFF0F4EC-126D-4B7A-B276-32850ABFEB56@gmail.com>

On 01/21/2016 01:16 AM, Khem Raj wrote:
>> On Jan 20, 2016, at 7:07 AM, Maxin B. John <maxin.john@intel.com> wrote:
>>
>> Hi,
>>
>> On Mon, Jan 11, 2016 at 08:30:32AM +0800, Hongxu Jia wrote:
>>> Update patches from debian
>>> http://ftp.de.debian.org/debian/pool/main/e/elfutils/elfutils_0.164-1.debian.tar.xz
>>>
>>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
>>> ---
>>> .../elfutils/elfutils-0.163/arm_func_value.patch   |  165 ----
>>> .../elfutils-0.163/arm_unwind_ret_mask.patch       |   83 --
>>> .../elfutils/elfutils-0.163/non_linux.patch        |   35 -
>>> .../elfutils-0.163/redhat-portability.diff         | 1021 --------------------
>>> .../elfutils/elfutils-0.163/scanf-format.patch     |   40 -
>>> .../uclibc-support-for-elfutils-0.161.patch        |  106 --
>>> ...ferences-between-mips-machine-identifiers.patch |   34 +
>>> ...m-Silence-Werror-maybe-uninitialized-fals.patch |    0
>>> .../0001-fix-a-stack-usage-warning.patch           |    0
>>> .../0001-remove-the-unneed-checking.patch          |    0
>>> ...-support-for-mips64-abis-in-mips_retval.c.patch |  168 ++++
>>> .../0003-Add-mips-n64-relocation-format-hack.patch |  226 +++++
>>> .../arm_backend.diff                               |  389 ++++----
>>> .../fixheadercheck.patch                           |    0
>>> .../hppa_backend.diff                              |   69 +-
>>> .../elfutils/elfutils-0.164/kfreebsd_path.patch    |   15 +
>>> .../m68k_backend.diff                              |   61 +-
>>> .../mips_backend.diff                              |   71 +-
>>> .../mips_readelf_w.patch                           |    8 +-
>>> .../testsuite-ignore-elflint.diff                  |    0
>>> .../{elfutils_0.163.bb => elfutils_0.164.bb}       |   15 +-
>>> 21 files changed, 735 insertions(+), 1771 deletions(-)
>>> delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.163/arm_func_value.patch
>>> delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.163/arm_unwind_ret_mask.patch
>>> delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.163/non_linux.patch
>>> delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.163/redhat-portability.diff
>>> delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.163/scanf-format.patch
>>> delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.163/uclibc-support-for-elfutils-0.161.patch
>> Here, the patch uclibc-support-for-elfutils-0.161.patch was removed.
>> However, it is still referenced in the recipe. It should be updated
>> to fix build error with uclibc.
>>
>> WARNING: Failed to fetch URL file://uclibc-support-for-elfutils-0.161.patch, attempting MIRRORS if available
>> ERROR: Fetcher failure: Unable to find file file://uclibc-support-for-elfutils-0.161.patch anywhere. The paths that were searched were:
>> …
> its already fixed in my musl pull request.

Oh, sorry for the incorrectly deleting, thanks Khem to fix it.

//Hongxu


>> Best Regards,
>> Maxin
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core



  reply	other threads:[~2016-01-21  3:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11  0:30 [PATCH 0/9] packages upgrade Hongxu Jia
2016-01-11  0:30 ` [PATCH 1/9] dhcp: 4.3.2 -> 4.3.3 Hongxu Jia
2016-01-11  0:30 ` [PATCH 2/9] elfutils: 0.163 -> 0.164 Hongxu Jia
2016-01-20 15:07   ` Maxin B. John
2016-01-20 17:16     ` Khem Raj
2016-01-21  3:23       ` Hongxu Jia [this message]
2016-01-11  0:30 ` [PATCH 3/9] pax-utils: 1.0.5 -> 1.1.4 Hongxu Jia
2016-01-12  1:14   ` Randy MacLeod
2016-01-12  1:22     ` Khem Raj
2016-01-12  2:38       ` Hongxu Jia
2016-01-11  0:30 ` [PATCH 4/9] xmlto: 0.0.26 -> 0.0.28 Hongxu Jia
2016-01-11  0:30 ` [PATCH 5/9] libgcrypt: 1.6.3 -> 1.6.4 Hongxu Jia
2016-01-11  0:30 ` [PATCH 6/9] ghostscript: 9.16 -> 9.18 Hongxu Jia
2016-01-12 11:39   ` Richard Purdie
2016-01-13  1:44     ` Hongxu Jia
2016-01-11  0:30 ` [PATCH 7/9] man-pages: 4.02 -> 4.04 Hongxu Jia
2016-01-11  0:30 ` [PATCH 8/9] help2man-native: 1.47.1 -> 1.47.3 Hongxu Jia
2016-01-11  0:30 ` [PATCH 9/9] gnupg: 2.1.7 -> 2.1.10 Hongxu Jia
2016-01-13  8:30 ` [PATCH V2] upgrade v2 pax-utils and v2 ghostscript Hongxu Jia
2016-01-13  8:30   ` [PATCH V2 3/9] pax-utils: 1.0.5 -> 1.1.4 Hongxu Jia
2016-01-13  8:30   ` [PATCH V2 6/9] ghostscript: 9.16 -> 9.18 Hongxu Jia
2016-01-17 17:44     ` Richard Purdie
2016-01-18  1:48       ` Hongxu Jia
2016-01-18  8:09       ` [PATCH V3 0/2] upgrade pax-utils and ghostscript Hongxu Jia
2016-01-18  8:09         ` [PATCH V2 1/2] pax-utils: 1.0.5 -> 1.1.4 Hongxu Jia
2016-01-18  8:09         ` [PATCH V3 2/2] ghostscript: 9.16 -> 9.18 Hongxu Jia
2016-01-13  8:48   ` [PATCH V2] upgrade v2 pax-utils and v2 ghostscript 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=56A04F3D.8000902@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=maxin.john@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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