From: "Peter A. Bigot" <pab@pabigot.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] git: add Git perl module to perltools package
Date: Thu, 25 Sep 2014 06:35:37 -0500 [thread overview]
Message-ID: <5423FE09.6020002@pabigot.com> (raw)
In-Reply-To: <1761684.on3aH1HNt7@peggleto-mobl5.ger.corp.intel.com>
On 09/25/2014 06:17 AM, Paul Eggleton wrote:
> On Thursday 25 September 2014 06:16:11 Peter A. Bigot wrote:
>> I'm at a loss here. The probable fix is clear and I can send it as
>> V2, but I can't test it: no matter what I do, "bitbake git-nativesdk"
>> succeeds after attemping 0 tasks of which 0 were required. This with
>> a completely clean build environment, no shared state enabled,
>> uninstalling git from the development machine, and removing
>> git-native from meta's ASSUME_PROVIDED (which allowed git-native to
>> build, but then said nothing PROVIDES git-nativesdk).
> Try: bitbake nativesdk-git
Thanks; that appears to be more productive.
Shouldn't I have gotten the nothing PROVIDES warning for git-nativesdk
even with git-native in ASSUME_PROVIDED? I'm smelling a missing
end-of-line anchor in a regex somewhere.
Peter
next prev parent reply other threads:[~2014-09-25 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 17:44 [PATCH] git: add Git perl module to perltools package Peter A. Bigot
2014-09-24 10:32 ` Peter A. Bigot
2014-09-25 10:49 ` Burton, Ross
2014-09-25 11:16 ` Peter A. Bigot
2014-09-25 11:17 ` Paul Eggleton
2014-09-25 11:35 ` Peter A. Bigot [this message]
2014-09-25 11:41 ` Burton, Ross
2014-09-25 11:23 ` Burton, Ross
2014-09-25 13:28 ` [PATCH v2] " Peter A. Bigot
2014-10-08 3:44 ` [PATCH] " 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=5423FE09.6020002@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 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.