Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Alexey Brodkin <alexey.brodkin@synopsys.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "marex@denx.de" <marex@denx.de>,
	"otavio@ossystems.com.br" <otavio@ossystems.com.br>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH v6] u-boot: Add mkenvimage tool
Date: Thu, 22 Nov 2018 13:42:30 +0000	[thread overview]
Message-ID: <ec8e8102f61407b19a6341a77858f7d825cab603.camel@linuxfoundation.org> (raw)
In-Reply-To: <dee5be3f45002c06f318bf633364aa842548cef8.camel@synopsys.com>

On Thu, 2018-11-22 at 13:18 +0000, Alexey Brodkin wrote:
> Hi, Richard, Otavio,
> 
> On Thu, 2018-11-22 at 11:28 +0300, Alexey Brodkin wrote:
> > This utility is used for creation of images containing
> > usable in run-time U-Boot environment.
> > 
> > As of today this utility is added per-board like here [1]
> > for Intel Edison board.
> > 
> > [1] 
> > http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/tree/meta-intel-edison-bsp/recipes-bsp/u-boot/u-boot-tools_2014.04.bb
> > 
> > Given there're quite some U-Boot tools that we may want to add
> > later
> > this recipe name switch from "u-boot-mkimage" to generic "u-boot-
> > tools"
> > still for compatibility we provide "u-boot-mkimage" with help
> > of PROVIDES as well as proposed "u-boot-mkenvimage".
> > 
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Cc: Otavio Salvador <otavio@ossystems.com.br>
> > Cc: Martin Jansa <martin.jansa@gmail.com>
> > Cc: Ross Burton <ross.burton@intel.com>
> > Cc: Marek Vasut <marex@denx.de>
> > ---
> > 
> > Changes v5 -> v6:
> >  * Really enable separate  pakaging of mkimage and mkenvimage
> > 
> > Changes v4 -> v5:
> >  * Added backward compatibility with "u-boot-mkimage" recipe
> >  * Improved handling of nativesdk
> >  * Update all references from "u-boot-mkimage" to "u-boot-tools"
> > 
> > Changes v3 -> v4:
> >  * Updated maintainer info to make Yocto autobuilder happy again
> > 
> > Changes v2 -> v3:
> >  * Recipe renamed to "u-boot-tools" to better match its contents
> >    (especially in the future as we add more tools there)
> >  * Existing "u-boot-mkimage" and newly introduced "u-boot-
> > mkenvimage"
> >    made avaialble via PROVIDES
> > 
> > Changes v1 -> v2:
> >  * Got rid of a separate recipe and instead added mkenvimage
> >    to u-boot mkimage recipe
> 
> So apparently something is still broken :(
> ------------------------->8-------------------------------
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'u-boot-tools-native-mkimage-native' (but
> virtual:native:.../openembedded-core/meta/recipes-bsp/u-boot/u-boot-
> tools_2018.07.bb RDEPENDS on or otherwise requires it)
> 
> NOTE: Runtime target 'u-boot-tools-native-mkimage-native' is
> unbuildable, removing...
> Missing or unbuildable dependency chain was: ['u-boot-tools-native-
> mkimage-native']
> 
> ERROR: Required build target 'core-image-base' has no buildable
> providers.
> Missing or unbuildable dependency chain was: ['core-image-base',
> 'virtual/kernel', 'u-boot-tools-native', 'u-boot-tools-native-
> mkimage-native']
> ------------------------->8-------------------------------
> 
> Indeed "u-boot-tools-native-mkimage-native" looks quite odd.
> 
> Any hints on how that could be addressed?

Just guessing but maybe

RDEPENDS_${PN}_class-native = ""

?

Cheers,

Richard



      reply	other threads:[~2018-11-22 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  8:28 [PATCH v6] u-boot: Add mkenvimage tool Alexey Brodkin
2018-11-22  9:30 ` Otavio Salvador
2018-11-22  9:47   ` Alexey Brodkin
2018-11-25 15:28     ` Andrea Galbusera
2018-11-22 13:18 ` Alexey Brodkin
2018-11-22 13:42   ` richard.purdie [this message]

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=ec8e8102f61407b19a6341a77858f7d825cab603.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexey.brodkin@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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