From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Denys Dmytriyenko <denys@ti.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] u-boot: update to version 2015.01
Date: Tue, 10 Feb 2015 11:26:22 -0500 [thread overview]
Message-ID: <20150210162622.GB14949@denix.org> (raw)
In-Reply-To: <CAJTo0LZHiTSkhv9YPobmssY_szH4jyzBeUXVyZnnTGYo5oAf4Q@mail.gmail.com>
On Tue, Feb 10, 2015 at 04:16:00PM +0000, Burton, Ross wrote:
> Hi Denys,
>
> On 10 February 2015 at 16:02, Denys Dmytriyenko <denis@denix.org> wrote:
>
> > +DEPENDS = "openssl"
> > +DEPENDS_class-native = "openssl-native"
> >
>
> That *really* shouldn't be required. :(
>
> And indeed, the old patch with -e shows that it isn't:
Yes, I understand it completely and my tests show the same exact -e output.
But since there were no other suggestions, I decided to cheat a bit... :)
> # $DEPENDS [6 operations]
> # set /home/ross/Yocto/poky/meta/conf/bitbake.conf:246
> # ""
> # set /home/ross/Yocto/poky/meta/conf/documentation.conf:135
> # [doc] "Lists a recipe's build-time dependencies (i.e. other recipe
> files)."
> # _prepend /home/ross/Yocto/poky/meta/classes/base.bbclass:81
> # "${BASEDEPENDS} "
> # set /home/ross/Yocto/poky/meta/recipes-bsp/u-boot/
> u-boot-mkimage_2015.01.bb:6
> # "openssl"
> # set native_virtclass_handler(e):27 [map_dependencies]
> # "openssl-native"
> # set data_smart.py:437 [finalize]
> # "${BASEDEPENDS} openssl-native"
> # pre-expansion value:
> # "${BASEDEPENDS} openssl-native"
> DEPENDS=" openssl-native"
>
> This is *very* strange. When the AB is free I'll do another rebuild to see
> what happens under load.
Thanks a lot! Looking forward for the results.
> Was the DEPENDS_class-native change the only difference between v1 and v2?
Yes, that was the only change.
--
Denys
next prev parent reply other threads:[~2015-02-10 16:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 16:02 [PATCH v2] u-boot: update to version 2015.01 Denys Dmytriyenko
2015-02-10 16:16 ` Burton, Ross
2015-02-10 16:17 ` Otavio Salvador
2015-02-10 16:29 ` Denys Dmytriyenko
2015-02-10 16:38 ` Burton, Ross
2015-02-10 16:48 ` Burton, Ross
2015-02-10 17:09 ` Denys Dmytriyenko
2015-02-10 17:12 ` Burton, Ross
2015-02-10 16:26 ` Denys Dmytriyenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-29 14:07 Denys Dmytriyenko
2015-01-29 19:33 ` Denys Dmytriyenko
2015-01-29 19:59 ` Burton, Ross
2015-01-29 20:06 ` Denys Dmytriyenko
2015-02-10 16:03 ` Denys Dmytriyenko
2015-01-23 22:40 Denys Dmytriyenko
2015-01-26 17:13 ` Denys Dmytriyenko
2015-01-26 17:15 ` Burton, Ross
2015-01-26 17:17 ` Otavio Salvador
2015-01-29 13:19 ` Burton, Ross
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=20150210162622.GB14949@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox