From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Why does building an image for machine X delete the bootloader for machine Y?
Date: Wed, 26 Nov 2014 05:14:31 -0700 [thread overview]
Message-ID: <5475C427.10008@mlbassoc.com> (raw)
In-Reply-To: <54758D01.3070601@topic.nl>
On 2014-11-26 01:19, Mike Looijmans wrote:
> I do a:
>
> MACHINE=X bitbake my-image
>
> This DEPENDS on a virtual bootloader, which will produce a BOOT.BIN file in the deploy directory, which is tmp-glibc/deploy.images/X/
>
> If I then do a:
>
> MACHINE=Y bitbake my-image
>
> the BOOT.BIN in tmp-glibc/deploy.images/X/ is suddenly gone!
>
> If i do a
>
> MACHINE=X bitbake my-image
>
> then the the BOOT.BIN in tmp-glibc/deploy.images/Y/ is suddenly gone, and the one for the X machine appears again. The bootloader recipe is not being rebuilt at all.
>
> The machines have the same MACHINE_ARCH, they differ on only minor points (the FPGA).
>
> What is going on here?
>
What machines are you building for? I've built for two different
i.MX6 platforms in the same build tree and I don't see this behaviour.
n.b. this was using the latest master Poky/Yocto
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2014-11-26 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 8:19 Why does building an image for machine X delete the bootloader for machine Y? Mike Looijmans
2014-11-26 11:31 ` Paul Eggleton
2014-11-26 13:20 ` Mike Looijmans
2014-11-26 14:57 ` Paul Eggleton
2014-11-26 18:44 ` Mike Looijmans
2014-11-27 7:46 ` Why does building an image for machine X delete the bootloader (and kernel) " Mike Looijmans
2014-11-27 8:20 ` Mike Looijmans
2014-11-26 12:14 ` Gary Thomas [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=5475C427.10008@mlbassoc.com \
--to=gary@mlbassoc.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