u-boot-fw-utils -> u-boot-fw-utils-cross
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
Signature · 2 lines
Anders Darander ChargeStorm AB / eStorm AB
Quoted 3 lines · Anders Darander
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.
Right.
Quoted 8 lines
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_printenvis 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 undertools/using HOSTC.
Yes; this is intended to be used in the host. I can add support for use in target as well (or help you to do it).
Quoted 2 lines
What's the reason for this change? Currently
fw_printenvis being built for my host system, and not the target...
Yes; the way to proper package it for target is from u-boot itself, not on this recipe.
Quoted 5 lines
Further more,
fw_printenvdoes not get packaged. I can see thatfw_printenvis installed in ${WORKDIR}/image, but never moved to ${WORKDIR}/package. I guess that this is caused by inheriting cross.bbclass?
Quoted 7 lines
Am I missing something in my distro config, or have I overlooked something else?
fw_printenvdoesn'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?
No, you are right. I can help you to solve it (or solve it and send you the solution) if you want.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 9 lines · Otavio Salvador
Quoted 3 lines · Anders Darander
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.
Right.
Quoted 3 lines
In my old branch, I used u-boot-fw-utils_2011.06. This used to compile and package
fw_printenv(setenv)just fine.
Quoted 7 lines
Quoted 5 lines
In the new, u-boot-fw-utils-cross_2013.07.bb,
fw_printenvis 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 undertools/using HOSTC.Yes; this is intended to be used in the host. I can add support for use in target as well (or help you to do it).
Honestly I do not understand this change at all? fw_printenv typically *always* executes on the target since it dumps the contents of the U-boot environment from a shell. Why would you want to build it for the host? That does not make sense. Unless host is the same as your target which I doubt could be considered the normal case, or?
Thanks.
Hans
Quoted 20 lines
Quoted 2 lines
What's the reason for this change? Currently
fw_printenvis being built for my host system, and not the target...Yes; the way to proper package it for target is from u-boot itself, not on this recipe.
Quoted 5 lines
Further more,
fw_printenvdoes not get packaged. I can see thatfw_printenvis installed in ${WORKDIR}/image, but never moved to ${WORKDIR}/package. I guess that this is caused by inheriting cross.bbclass?Quoted 7 lines
Am I missing something in my distro config, or have I overlooked something else?
fw_printenvdoesn'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?
No, you are right. I can help you to solve it (or solve it and send you the solution) if you want.
Quoted 20 lines · Hans Beckerus
Quoted 19 lines · Otavio Salvador
Quoted 4 lines · Anders Darander
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.
Right.
Quoted 8 lines
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_printenvis 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 undertools/using HOSTC.
Quoted 8 lines
Quoted 2 lines
Yes; this is intended to be used in the host. I can add support for use in target as well (or help you to do it).
Honestly I do not understand this change at all?
fw_printenvtypically *always* executes on the target since it dumps the contents of the U-boot environment from a shell. Why would you want to build it for the host? That does not make sense. Unless host is the same as your target which I doubt could be considered the normal case, or?
It depends on how do you intend to use this. It can be used to mangle environment during image processing.
I will cook a patch and send for testing, so we get target ones back.
Regards,
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 13 lines · Otavio Salvador
Quoted 3 lines · Anders Darander
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.
Right.
Quoted 1 line
In my old branch, I used u-boot-fw-utils_2011.06. This used to
compile
Quoted 3 lines
and package
fw_printenv(setenv)just fine.In the new, u-boot-fw-utils-cross_2013.07.bb,
fw_printenvis now
Quoted 8 lines
built
Quoted 4 lines
using HOSTCC instead of the cross-compiler. The old recipe used to include:
EXTRA_OEMAKE= 'HOSTCC="${CC}"'
as u-boot defaults to build everything undertools/using HOSTC.Yes; this is intended to be used in the host. I can add support for use in target as well (or help you to do it).
Sorry that I didn't see this during the review of your patch that made this change. If u-boot-fw-utils-cross of intended to be used on the host, why did you then replace the old u-boot-fw-utils with this recipe?
The old u-boot-fw-utils were to create fw_printenv to be used on the _target_ not on the host. Unfortunately, I don't think this was ever mentioned during the patch review...
Quoted 6 lines
Quoted 1 line
What's the reason for this change? Currently
fw_printenvis beingbuilt
Quoted 1 line
for my host system, and not the target...
Yes; the way to proper package it for target is from u-boot itself, not on this recipe.
Yep, so the commit log that makes the transition from u-boot-fw-utils to u-boot-fw-utils-cross should have mentioned that the purpose of those two packages are completely different.
Quoted 10 lines
Quoted 7 lines
Further more,
fw_printenvdoes not get packaged. I can see thatfw_printenvis 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_printenvdoesn't really make sense for me to runon
Quoted 2 lines
the host, and is (in my case) rather essential on the target.
Quoted 7 lines
Quoted 1 line
I guess that I'm doing something wrong; can anyone give me some hint
on
Quoted 2 lines
where to look? Or do we have an issue with the u-boot-fw-utils-cross recipe?
No, you are right. I can help you to solve it (or solve it and send you the solution) if you want.
I've got a working u-boot-fw-utils recipe that I can submit. I'll look into this on Monday morning, to ensure that it's of enough quality to publish.
Just curious, what use case do you have for fw_* the build host?
Cheers,
Anders
Signature · 1 line
ChargeStorm AB / eStorm
Quoted 20 lines · Anders Darander
Quoted 19 lines · Otavio Salvador
Quoted 3 lines · Anders Darander
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.
Right.
Quoted 1 line
In my old branch, I used u-boot-fw-utils_2011.06. This used to
compile
Quoted 3 lines
and package
fw_printenv(setenv)just fine.In the new, u-boot-fw-utils-cross_2013.07.bb,
fw_printenvis nowbuilt
Quoted 4 lines
using HOSTCC instead of the cross-compiler. The old recipe used to include:
EXTRA_OEMAKE= 'HOSTCC="${CC}"'
as u-boot defaults to build everything undertools/using HOSTC.
Quoted 6 lines
Quoted 2 lines
Yes; this is intended to be used in the host. I can add support for use in target as well (or help you to do it).
Sorry that I didn't see this during the review of your patch that made this change. If u-boot-fw-utils-cross of intended to be used on the host, why did you then replace the old u-boot-fw-utils with this recipe?
The old u-boot-fw-utils were to create
fw_printenvto be used on the _target_ not on the host. Unfortunately, I don't think this was ever mentioned during the patch review...
Yes but this was a /bug/ in the build system. As it got HOSTCC so it was indeed to be used as /host/ not target.
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
What's the reason for this change? Currently
fw_printenvis beingbuilt
Quoted 1 line
for my host system, and not the target...
Yes; the way to proper package it for target is from u-boot itself, not on this recipe.
Yep, so the commit log that makes the transition from u-boot-fw-utils to u-boot-fw-utils-cross should have mentioned that the purpose of those two packages are completely different.
Right; I might not been clear on this.
Quoted 11 lines
Quoted 11 lines
Quoted 7 lines
Further more,
fw_printenvdoes not get packaged. I can see thatfw_printenvis 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_printenvdoesn't really make sense for me to runon
Quoted 3 lines
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
Quoted 8 lines
Quoted 6 lines
on
Quoted 2 lines
where to look? Or do we have an issue with the u-boot-fw-utils-cross recipe?
No, you are right. I can help you to solve it (or solve it and send you the solution) if you want.
I've got a working u-boot-fw-utils recipe that I can submit. I'll look into this on Monday morning, to ensure that it's of enough quality to publish.
Ahh neat! So please e-mail me and I help to clean it.
Quoted 1 line
Just curious, what use case do you have for fw_* the build host?
So we can mangle environment per image ;-)
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 24 lines · Otavio Salvador
Quoted 22 lines · Anders Darander
Quoted 21 lines · Otavio Salvador
Quoted 3 lines · Anders Darander
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.
Right.
Quoted 1 line
In my old branch, I used u-boot-fw-utils_2011.06. This used to
compile
Quoted 3 lines
and package
fw_printenv(setenv)just fine.In the new, u-boot-fw-utils-cross_2013.07.bb,
fw_printenvis nowbuilt
Quoted 4 lines
using HOSTCC instead of the cross-compiler. The old recipe used to include:
EXTRA_OEMAKE= 'HOSTCC="${CC}"'
as u-boot defaults to build everything undertools/using HOSTC.Yes; this is intended to be used in the host. I can add support for use in target as well (or help you to do it).
Quoted 6 lines
Quoted 3 lines
Sorry that I didn't see this during the review of your patch that made this change. If u-boot-fw-utils-cross of intended to be used on the host, why did you then replace the old u-boot-fw-utils with this recipe?
The old u-boot-fw-utils were to create
fw_printenvto be used on the _target_ not on the host. Unfortunately, I don't think this was ever mentioned during the patch review...Yes but this was a /bug/ in the build system. As it got HOSTCC so it was indeed to be used as /host/ not target.
Well, the fw_printenv is indeed mainly intended to be used on target... Why the U-Boot maintainers insist on defaulting to use HOSTCC is a completely different matter. I know that there's been quite a few mail threads about that (and I've personally argued on this matter in at least one of those threads). Thus, I don't agree with you that it was a bug in the original recipe.
I'm doing the same thing in my patch, as I prefer to do it that way instead of patching the Makefile.
Quoted 26 lines
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
What's the reason for this change? Currently
fw_printenvis beingbuilt
Quoted 1 line
for my host system, and not the target...
Yes; the way to proper package it for target is from u-boot itself, not on this recipe.
Yep, so the commit log that makes the transition from u-boot-fw-utils to u-boot-fw-utils-cross should have mentioned that the purpose of those two packages are completely different.
Right; I might not been clear on this.
Quoted 14 lines
Quoted 14 lines
Quoted 7 lines
Further more,
fw_printenvdoes not get packaged. I can see thatfw_printenvis 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_printenvdoesn't really make sense for me to runon
Quoted 3 lines
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
Quoted 2 lines
where to look? Or do we have an issue with the u-boot-fw-utils-cross recipe?
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
No, you are right. I can help you to solve it (or solve it and send you the solution) if you want.
I've got a working u-boot-fw-utils recipe that I can submit. I'll look into this on Monday morning, to ensure that it's of enough quality to publish.
Ahh neat! So please e-mail me and I help to clean it.
I've made a quick clean-up and submitted a patch a few moments ago. Hopefully, I might have some review comments by Monday, which hopefully could get the patch to a mergeable state during Monday / Tuesday.
Quoted 3 lines
Quoted 1 line
Just curious, what use case do you have for fw_* the build host?
So we can mangle environment per image ;-)
Ok. I've never tried to do that using these tools. The only times I've created env-images, I've been using an old TCL script based on the one Atmel supplies in their SAM-BA tool...
Cheers,
Anders
Signature · 4 lines
Anders Darander ChargeStorm AB Tel: +46 702 44 84 36 Laxholmstorget 3 Email: [email protected] 602 21 Norrköping Web: www.chargestorm.se