From: Anders Darander <anders@chargestorm.se>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: u-boot-fw-utils -> u-boot-fw-utils-cross
Date: Fri, 13 Sep 2013 09:56:36 +0200 [thread overview]
Message-ID: <20130913075635.GA3573@ad.chargestorm.se> (raw)
Hi,
As I've started to bring our internal distro and machines up to the
lates oe-core, I've got some issues with the u-boot-fw-utils to
u-boot-fw-utils-cross transition.
In my old branch, I used u-boot-fw-utils_2011.06. This used to compile
and package fw_printenv(setenv) just fine.
In the new, u-boot-fw-utils-cross_2013.07.bb, fw_printenv is now built
using HOSTCC instead of the cross-compiler. The old recipe used to
include:
EXTRA_OEMAKE = 'HOSTCC="${CC}"'
as u-boot defaults to build everything under tools/ using HOSTC.
What's the reason for this change? Currently fw_printenv is being built
for my host system, and not the target...
Further more, fw_printenv does not get packaged. I can see that
fw_printenv is installed in ${WORKDIR}/image, but never moved to
${WORKDIR}/package. I guess that this is caused by inheriting
cross.bbclass?
Am I missing something in my distro config, or have I overlooked
something else? fw_printenv doesn't really make sense for me to run on
the host, and is (in my case) rather essential on the target.
I guess that I'm doing something wrong; can anyone give me some hint on
where to look? Or do we have an issue with the u-boot-fw-utils-cross
recipe?
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
next reply other threads:[~2013-09-13 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 7:56 Anders Darander [this message]
2013-09-13 17:32 ` u-boot-fw-utils -> u-boot-fw-utils-cross Otavio Salvador
2013-09-13 17:58 ` Hans Beckerus
2013-09-13 18:35 ` Otavio Salvador
2013-09-13 18:55 ` Anders Darander
2013-09-13 19:16 ` Otavio Salvador
2013-09-13 19:29 ` Anders Darander
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=20130913075635.GA3573@ad.chargestorm.se \
--to=anders@chargestorm.se \
--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