All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [BBCLASSEXTEND BUG?] Not taking virtual:native provider into account?
Date: Sun, 21 Feb 2010 17:40:48 +0100	[thread overview]
Message-ID: <20100221164048.GU30265@mx.loc> (raw)

Hi,

I'm using bitbake 641e6cf3ec3ab4d26929cf4d2a3704ff07eed4d6 (current
HEAD) on HEAD of oe.

I'm adding:
$ cat recipes/git/git_1.7.0.bb 
require git.inc
SRC_URI[git.md5sum] = "c7553b73e2156d187ece6ba936ae30ab"
SRC_URI[git.sha256sum] = "a61e863944381c4f8231841f678f41f56b634bebca486a61005b35e5bcbb7c79"
DEPENDS = "openssl curl zlib expat"
RDEPENDS = "perl perl-module-file-path cpio findutils sed"
PR = "r0"
FILES_${PN}-dbg += "${libexecdir}/git-core/.debug"
BBCLASSEXTEND = "native"

(and add ";name=git" to the .tar in git.inc's SRC_URI)
and bake git-native and see:
DEBUG: adding .../recipes/git/git-native_1.6.0.4.bb to satisfy git-native
instead of
DEBUG: adding virtual:native:.../recipes/git/git_1.7.0.bb to satisfy git-native
which i get if i rm git-native_*

Assuming that the aboce recipe is correct in principle, this somehow
sounds like BBCLASSEXTEND'ed virtual:native never make it into
providers. What am i doing wrong?

thanks and cheers,
Bernhard



             reply	other threads:[~2010-02-21 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 16:40 Bernhard Reutner-Fischer [this message]
2010-02-22 12:40 ` [BBCLASSEXTEND BUG?] Not taking virtual:native provider into account? Richard Purdie
2010-02-22 13:10   ` Bernhard Reutner-Fischer
2010-02-22 17:15     ` Tom Rini

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=20100221164048.GU30265@mx.loc \
    --to=rep.dot.nop@gmail.com \
    --cc=openembedded-devel@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 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.