From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 7/9] btrfs-tools: 3.18.2 -> 4.0.1
Date: Fri, 29 May 2015 14:36:32 +0100 [thread overview]
Message-ID: <1432906592.404.138.camel@linuxfoundation.org> (raw)
In-Reply-To: <9267553a2f080dfb2fac0522df25346195b831fa.1432805258.git.liezhi.yang@windriver.com>
On Thu, 2015-05-28 at 02:57 -0700, Robert Yang wrote:
> * Updated fix-parallel.patch
> * inherit autotools-brokensep, the autotools doesn't work:
> | make: *** No rule to make target `ctree.o', needed by `btrfs'. Stop.
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> .../btrfs-tools/btrfs-tools/fix-parallel.patch | 16 ++++++++--------
> .../btrfs-tools/btrfs-tools_git.bb | 16 +++++++++-------
> 2 files changed, 17 insertions(+), 15 deletions(-)
Did upstream switch to autotools for 4.x? If so, this should really be
mentioned in the commit message to make sense of the changes.
Cheers,
Richard
next prev parent reply other threads:[~2015-05-29 13:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:57 [PATCH 0/9] Packages Upgrade Robert Yang
2015-05-28 9:57 ` [PATCH 1/9] debianutils: 4.4 -> 4.5 Robert Yang
2015-05-28 9:57 ` [PATCH 2/9] git: 2.3.7 -> 2.4.2 Robert Yang
2015-05-28 9:57 ` [PATCH 3/9] python-git: 1.0.0 -> 1.0.1 Robert Yang
2015-05-28 9:57 ` [PATCH 4/9] cracklib: 2.9.3 -> 2.9.4 Robert Yang
2015-05-28 9:57 ` [PATCH 5/9] man-pages: 3.83 -> 4.00 Robert Yang
2015-05-28 9:57 ` [PATCH 6/9] gnupg: 2.1.2 -> 2.1.4 Robert Yang
2015-05-28 9:57 ` [PATCH 7/9] btrfs-tools: 3.18.2 -> 4.0.1 Robert Yang
2015-05-29 13:36 ` Richard Purdie [this message]
2015-06-01 2:38 ` Robert Yang
2015-05-28 9:57 ` [PATCH 8/9] nasm: 2.11.06 -> 2.11.08 Robert Yang
2015-05-28 9:57 ` [PATCH 9/9] lttng-ust: 2.6.0 -> 2.6.1 Robert Yang
2015-05-28 10:03 ` Martin Jansa
2015-05-29 1:31 ` Robert Yang
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=1432906592.404.138.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox