On Fri, Jan 22, 2016 at 4:39 AM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 17 January 2016 at 11:36, Khem Raj <raj.k...@gmail.com> wrote: >> >> musl does not support backtrace APIs >> include limit.h for PATH_MAX definition >> >> Signed-off-by: Khem Raj <raj.k...@gmail.com> > > > Since the rebase to btrfs-tools 4.4 this fails to patch: > > NOTE: Applying patch '0001-btrfs-corrupt-blocks-Include-limits.h.patch' > (../meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-corrupt-blocks-Include-limits.h.patch) > ERROR: Command Error: exit status: 1 Output: > Applying patch 0001-btrfs-corrupt-blocks-Include-limits.h.patch > patching file btrfs-corrupt-block.c > Hunk #1 FAILED at 21. > 1 out of 1 hunk FAILED -- rejects in file btrfs-corrupt-block.c > Patch 0001-btrfs-corrupt-blocks-Include-limits.h.patch can be > reverse-applied > > Presumably 4.4 accepted these patches and this can be dropped?
Patch part is in upstream so can be dropped however there is a recipe change which is still needed > > Ross -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
