|
Weekly Test Report for Yocto 1.4 20130213 Build
Stoicescu, CorneliuX <corneliux.stoicescu@...>
Hello,
As described in a previous mail regarding the automated real-time reports, here is this the report for the current weekly build:
https://wiki.yoctoproject.org/wiki/Weekly_Test_Report_for_Yocto_1.4_20130213_Build
This is a static page.
Here is the status of the real-time reporting tool:
-the information in the report is extracted directly and in real-time from Testopia (https://wiki.yoctoproject.org/wiki/Testopia )
-pages are derived from a template for each branch (ex: for master we have this template:
https://wiki.yoctoproject.org/wiki/QA_Status_TEMPLATE)
-the template can be changed/improved at any time
-from the template we can create reports for any build by editing it and replacing the TEMPLATE Test Runs with actual Test Runs from the current build (using the run_id field)
-the next step will be to fully automate this report and make it extract the test runs needed based on the last build inserted into Testopia. This will be fully functional in Q2. Until then I need to get as much feedback as possible on
how the report should look and what information it should contain.
-after automation, a wiki page will be created with usage instructions for this extension. Even though this extension has some documentation on the net, it is not of much use. I have heavily modified it by removing/adding features, fields
and parameters. The goal is to fully personalize it for us.
Thank you for the support ! If you have any questions or concerns, please contact me.
Regards,
Cornel
|
|
|
Flanagan, Elizabeth <elizabeth.flanagan@...>
On Wed, Feb 20, 2013 at 4:51 AM, Richard Purdie <richard.purdie@...> wrote: On Tue, 2013-02-19 at 21:01 -0800, Flanagan, Elizabeth wrote:
I'm currently at ELC and am going to be a little slow with email.
However, tonight I will be building M4 rc1. We are looking pretty
green and had been hoping to use the last build for rc1, but we want
to get it a little closer as to have it all green. I will be building
it from current master head and will branch/tag in the morning. If you
maintain a layer that I don't have branch access for, please create
the milestone branch for it from the git hashes I send out in the
morning. Thanks. We continued to have a build issue which I traced back to the recent
bitbake fetcher changes. I've reverted a part of that and rebuilt master
and its looking even better than the previous build, lots of green. I
think we'll therefore be going with that revision
(7d22ef28e64de06b6238d0ef9b664c0bee6efa46) for M4-rc1, assuming the rest
builds out ok. It looks like we have a good buildout. I'll get branches prepared/tagged and pushed later today. Please begin testing http://autobuilder.yoctoproject.org/pub/nightly/20130220-2. -b
Cheers,
Richard
-- Elizabeth Flanagan Yocto Project Build and Release
|
|
|
Re: Updated Yocto Hands-on Kernel Lab available
Tom Zanussi <tom.zanussi@...>
On Tue, 2013-02-19 at 22:34 -0500, Trevor Woerner wrote: Following up on a hunch, after reading Pierre Ficheux's email from
earlier today, I realized that by default I always switch my build's
PACKAGE_CLASSES to ipk simply because this packaging takes the least
amount of build time. Sure enough, when working on lab3 I had switched
to ipk and it didn't work. Switching PACKAGE_CLASSES to rpm and doing
nothing else but rebuilding, everything worked. I tried twice more
switching between ipk and rpm and anytime ipk is used the module is
not automatically installed, but with rpm it is. Interesting - I wouldn't have thought of looking at that as a source of the problem. I'll try it out myself and file a bug if it turns out to be the problem. Thanks for that info! Tom
|
|
|
Re: Updating uboot to v2013.01
Satya Swaroop Damarla <swaroop.damarla@...>
hey Guys... I get the following error... which I attached.. Its completely greek and latin to me.. Can you please help me..
On Wed, Feb 20, 2013 at 7:19 PM, Satya Swaroop DAMARLA <swaroop@...> wrote:
hey Guys... I get the following error... which I attached.. Its completely greek and latin to me.. Can you please help me..
|
|
|
Re: Updating uboot to v2013.01
Satya Swaroop DAMARLA <swaroop@...>
hey Guys... I get the following error... which I attached.. Its completely greek and latin to me.. Can you please help me..
On Wed, Feb 20, 2013 at 6:46 PM, Hans Beckérus <hans.beckerus@...> wrote:
On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla
< swaroop.damarla@...> wrote:
> Hey hans, this is what he meant,
>
> In the machine config file add the following
>
> PREFERRED_VERSION_u-boot ?= "v2013.01%" or PREFERRED_VERSION_u-boot ?=
> "v2013.01.01%"
>
> By the way did you already complete the first part... There is also other
> file called " u-boot-fw-utils_2012.04.01.bb" ... I think we should do the
> same...
>
> Hans bytheway, are you also working on the same board or diffferent board
> with same problem?
>
Now I get it. Thanks. But still question remains how in earth I
managed to build the kernel if not also having copied/renamed the
mkimage .bb?
Is the PREFERRED_VERSION_u-boot used to determine what mkimage and fw
utils it picks up?
Then it might be that since I/we build u-boot as a separate package,
but kernel lifts in the mkimage stuff, it works but the wrong package
was used.
In my case obviously compatible, but not recommended I guess. Also, I
agree that the fw utils should probably be in sync similar to mkimage.
Hans
>
>
>
>
>
> On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus < hans.beckerus@...>
> wrote:
>>
>> On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
>> < rstreif@...> wrote:
>> > Satya,
>> >
>> > Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
>> > u-boot_2012.04.01.bb. You can simply copy it and name it
>> > u-boot_2013.01.bb
>> > and then modify SRCREV to the revision that corresponds to the tag
>> > 2013.01
>> > or 2013.01.01 in git.denx.de:
>> >
>> > for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
>> > for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
>> >
>> > Do the same for u-boot-mkimage and include the u-boot version with your
>> > bsp.
>> >
>> > Rudi
>> >
>> >
>> Hi Rudi, sorry to chime in , but I have a similar problem but do not
>> really get the last thing you said.
>> What do you mean by including the u-boot version in the bsp? Also is
>> it a must to also copy the mkimage .bb or will the system find a
>> suitable one automatically?
>> The thing is that I only copied/edited the u-boot .bb but never the
>> mkimage. Still my kernel successfully builds the kernel uImage!?
>> Some magic that I have missed :)
>>
>> Hans
>>
>>
>> > On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
>> > < swaroop.damarla@...> wrote:
>> >>
>> >> Hi Guys,
>> >>
>> >> I need support for uboot on Tamonten board but the version on it is
>> >> v2012.04 but I came to know that v2012.10 or v2013.01 supports the
>> >> Tamontenboard through some guys here..
>> >>
>> >> It would be great if you can tell me how can I accomplish v2013.01 or
>> >> v2012.10 into the build system and make it available so that I can
>> >> compile
>> >> the and get uImage
>> >>
>> >> (Tamonten board is a derivative of harmony board with some changes and
>> >> has
>> >> arm cortexa9 processor without neon extentions )
>> >>
>> >> I am kind of new to add new .bb files and help is really appreciated as
>> >> I
>> >> am not able to figure out how to add
>> >>
>> >> Greetings & Regards,
>> >> Swaroop
>> >>
>> >> _______________________________________________
>> >> yocto mailing list
>> >> yocto@...
>> >> https://lists.yoctoproject.org/listinfo/yocto
>> >>
>> >
>> >
>> >
>> > --
>> > --
>> > Rudolf J. Streif
>> > Director of Embedded Solutions
>> > The Linux Foundation
>> >
>> > rudolf.streif@...
>> > Phone: +1.619.631.5383
>> > Skype: rudolfstreif
>> > PGP: RSA 2048/2048 D6E7D28B
>> >
>> > Linux Foundation Events Schedule: events.linuxfoundation.org
>> > Linux Foundation Training Schedule: training.linuxfoundation.org
>> >
>> >
>> > _______________________________________________
>> > yocto mailing list
>> > yocto@...
>> > https://lists.yoctoproject.org/listinfo/yocto
>> >
>
>
|
|
|
Re: bitbake: how to resolve a dependency to kernel-devicetree when building rootfs
Hans Beckérus <hans.beckerus@...>
On Wed, Feb 20, 2013 at 8:33 AM, Frans Meulenbroeks <fransmeulenbroeks@...> wrote: Is there a kernel-devicetree package in you tmp/deploy ?
I'm using ipk and I have:
tmp/deploy/ipk/syrcxx/kernel-devicetree_2.6.38-r4_syrcxx.ipk
If it is not there that is your problem.
You may also want to nuke your tmp dir and rebuild (with sstate it should
not take excessively long)
Frans
Thanks for the pointer. That was indeed the problem. There was no kernel-devicetree in my deploy/ipk folder. But now it works :) I actually did two things, I moved from using .ipk to .rpm and changed to using a bare danny 8.0. I do not know which of these fixed it. Before that I also tried to nuke the tmp dir but that was fruitless :( Hans
2013/2/19 Hans Beckérus <hans.beckerus@...>
First of all, I am a total noob when it comes to bitbake, but I am
struggling and slowly getting there ( I think).
So, I am sorry if my questions seems stupid, but this one I just can
not seem to figure out on my own.
What I am trying to do is to build a custom ARM based rootfs image
using the ELDK toolchain that should include all the modules from my
kernel build. But the rootfs build stage fails! If I exclude the
kernel modules everything work just fine.
The bitbake error I get is
| Collected errors:
| * satisfy_dependencies_for: Cannot satisfy the following
dependencies for kernel-modules:
| * kernel-devicetree *
| * opkg_install_cmd: Cannot install package kernel-modules.
My simple rootfs.bb looks like this
require recipes-core/images/core-image-minimal.bb
# The list of packages used to build images.
IMAGE_INSTALL += "kernel-modules"
# Formats of root filesystem images that you want to have created.
IMAGE_FSTYPES = "jffs2"
The device tree blob was built successfully and is located in the
kernel deploy image folder.
I can see that I have the following files under the kernel work path
./packages-split/kernel-devicetree
./pkgdata/runtime/kernel-devicetree
./pkgdata/runtime-reverse/kernel-devicetree
Any advice on what I have missed?
Hans
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
|
|
|
Re: Updating uboot to v2013.01
Hans Beckérus <hans.beckerus@...>
On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla <swaroop.damarla@...> wrote: Hey hans, this is what he meant,
In the machine config file add the following
PREFERRED_VERSION_u-boot ?= "v2013.01%" or PREFERRED_VERSION_u-boot ?=
"v2013.01.01%"
By the way did you already complete the first part... There is also other
file called "u-boot-fw-utils_2012.04.01.bb" ... I think we should do the
same...
Hans bytheway, are you also working on the same board or diffferent board
with same problem?
Different board, same core, similar problem ;) Now I get it. Thanks. But still question remains how in earth I managed to build the kernel if not also having copied/renamed the mkimage .bb? Is the PREFERRED_VERSION_u-boot used to determine what mkimage and fw utils it picks up? Then it might be that since I/we build u-boot as a separate package, but kernel lifts in the mkimage stuff, it works but the wrong package was used. In my case obviously compatible, but not recommended I guess. Also, I agree that the fw utils should probably be in sync similar to mkimage. Hans
On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus <hans.beckerus@...>
wrote:
On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
<rstreif@...> wrote:
Satya,
Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
u-boot_2012.04.01.bb. You can simply copy it and name it
u-boot_2013.01.bb
and then modify SRCREV to the revision that corresponds to the tag
2013.01
or 2013.01.01 in git.denx.de:
for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
Do the same for u-boot-mkimage and include the u-boot version with your
bsp.
Rudi
Hi Rudi, sorry to chime in , but I have a similar problem but do not
really get the last thing you said.
What do you mean by including the u-boot version in the bsp? Also is
it a must to also copy the mkimage .bb or will the system find a
suitable one automatically?
The thing is that I only copied/edited the u-boot .bb but never the
mkimage. Still my kernel successfully builds the kernel uImage!?
Some magic that I have missed :)
Hans
On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
<swaroop.damarla@...> wrote:
Hi Guys,
I need support for uboot on Tamonten board but the version on it is
v2012.04 but I came to know that v2012.10 or v2013.01 supports the
Tamontenboard through some guys here..
It would be great if you can tell me how can I accomplish v2013.01 or
v2012.10 into the build system and make it available so that I can
compile
the and get uImage
(Tamonten board is a derivative of harmony board with some changes and
has
arm cortexa9 processor without neon extentions )
I am kind of new to add new .bb files and help is really appreciated as
I
am not able to figure out how to add
Greetings & Regards,
Swaroop
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
--
Rudolf J. Streif
Director of Embedded Solutions
The Linux Foundation
rudolf.streif@...
Phone: +1.619.631.5383
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B
Linux Foundation Events Schedule: events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
|
|
|
Re: Updating uboot to v2013.01
Satya Swaroop Damarla <swaroop.damarla@...>
Hey hans, this is what he meant,
In the machine config file add the following
PREFERRED_VERSION_u-boot ?= "v2013.01%" or PREFERRED_VERSION_u-boot ?= "v2013.01.01%"
By the way did you already complete the first part... There is also other file called " u-boot-fw-utils_2012.04.01.bb" ... I think we should do the same...
Hans bytheway, are you also working on the same board or diffferent board with same problem?
On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus <hans.beckerus@...> wrote:
On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif
< rstreif@...> wrote:
> Satya,
>
> Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
> u-boot_2012.04.01.bb. You can simply copy it and name it u-boot_2013.01.bb
> and then modify SRCREV to the revision that corresponds to the tag 2013.01
> or 2013.01.01 in git.denx.de:
>
> for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
> for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
>
> Do the same for u-boot-mkimage and include the u-boot version with your bsp.
>
> Rudi
>
>
really get the last thing you said.
What do you mean by including the u-boot version in the bsp? Also is
it a must to also copy the mkimage .bb or will the system find a
suitable one automatically?
The thing is that I only copied/edited the u-boot .bb but never the
mkimage. Still my kernel successfully builds the kernel uImage!?
Some magic that I have missed :)
Hans
> On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
> < swaroop.damarla@...> wrote:
>>
>> Hi Guys,
>>
>> I need support for uboot on Tamonten board but the version on it is
>> v2012.04 but I came to know that v2012.10 or v2013.01 supports the
>> Tamontenboard through some guys here..
>>
>> It would be great if you can tell me how can I accomplish v2013.01 or
>> v2012.10 into the build system and make it available so that I can compile
>> the and get uImage
>>
>> (Tamonten board is a derivative of harmony board with some changes and has
>> arm cortexa9 processor without neon extentions )
>>
>> I am kind of new to add new .bb files and help is really appreciated as I
>> am not able to figure out how to add
>>
>> Greetings & Regards,
>> Swaroop
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@...
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
> --
> --
> Rudolf J. Streif
> Director of Embedded Solutions
> The Linux Foundation
>
> rudolf.streif@...
> Phone: +1.619.631.5383
> Skype: rudolfstreif
> PGP: RSA 2048/2048 D6E7D28B
>
> Linux Foundation Events Schedule: events.linuxfoundation.org
> Linux Foundation Training Schedule: training.linuxfoundation.org
>
>
> _______________________________________________
> yocto mailing list
> yocto@...
> https://lists.yoctoproject.org/listinfo/yocto
>
|
|
|
Re: Updating uboot to v2013.01
Hans Beckérus <hans.beckerus@...>
On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif <rstreif@...> wrote: Satya,
Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as
u-boot_2012.04.01.bb. You can simply copy it and name it u-boot_2013.01.bb
and then modify SRCREV to the revision that corresponds to the tag 2013.01
or 2013.01.01 in git.denx.de:
for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d
for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46
Do the same for u-boot-mkimage and include the u-boot version with your bsp.
Rudi
Hi Rudi, sorry to chime in , but I have a similar problem but do not really get the last thing you said. What do you mean by including the u-boot version in the bsp? Also is it a must to also copy the mkimage .bb or will the system find a suitable one automatically? The thing is that I only copied/edited the u-boot .bb but never the mkimage. Still my kernel successfully builds the kernel uImage!? Some magic that I have missed :) Hans On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla
<swaroop.damarla@...> wrote:
Hi Guys,
I need support for uboot on Tamonten board but the version on it is
v2012.04 but I came to know that v2012.10 or v2013.01 supports the
Tamontenboard through some guys here..
It would be great if you can tell me how can I accomplish v2013.01 or
v2012.10 into the build system and make it available so that I can compile
the and get uImage
(Tamonten board is a derivative of harmony board with some changes and has
arm cortexa9 processor without neon extentions )
I am kind of new to add new .bb files and help is really appreciated as I
am not able to figure out how to add
Greetings & Regards,
Swaroop
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
--
Rudolf J. Streif
Director of Embedded Solutions
The Linux Foundation
rudolf.streif@...
Phone: +1.619.631.5383
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B
Linux Foundation Events Schedule: events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
|
|
|
Re: Trying to compile mono on target for machine crownbay
Evgheni Antropov <aidjek@...>
In my case I have resolved it in another way:
correct in Makefile for "eglib" folder SUBDIRS variables and excluded "test"
from them values:
-----------------------------------------
egrep "SUBDIRS =" ./mono-2.10.2/build/eglib/Makefile
DIST_SUBDIRS = src test
SUBDIRS = src test
#SUBDIRS = src
#SUBDIRS = src
#SUBDIRS = src
+++++++++++++++++++++++++++++++++++++++++
egrep "SUBDIRS =" ./mono-2.10.2/build/eglib/Makefile
DIST_SUBDIRS = src
SUBDIRS = src
#SUBDIRS = src
#SUBDIRS = src
#SUBDIRS = src
"build" is my own directory where I'm compiling mono.
|
|
|
Re: Updating uboot to v2013.01
Rudolf Streif <rstreif@...>
Satya,
Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as u-boot_2012.04.01.bb. You can simply copy it and name it u-boot_2013.01.bb and then modify SRCREV to the revision that corresponds to the tag 2013.01 or 2013.01.01 in git.denx.de:
Do the same for u-boot-mkimage and include the u-boot version with your bsp.
Rudi
On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla <swaroop.damarla@...> wrote:
Hi Guys,
I need support for uboot on Tamonten board but the version on it is v2012.04 but I came to know that v2012.10 or v2013.01 supports the Tamontenboard through some guys here..
It would be great if you can tell me how can I accomplish v2013.01 or v2012.10 into the build system and make it available so that I can compile the and get uImage
(Tamonten board is a derivative of harmony board with some changes and has arm cortexa9 processor without neon extentions )
I am kind of new to add new .bb files and help is really appreciated as I am not able to figure out how to add
Greetings & Regards, Swaroop
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
-- -- Rudolf J. StreifDirector of Embedded Solutions
The Linux Foundation
Phone: +1.619.631.5383 Skype: rudolfstreif PGP: RSA 2048/2048 D6E7D28B
|
|
|
Updating uboot to v2013.01
Satya Swaroop Damarla <swaroop.damarla@...>
Hi Guys,
I need support for uboot on Tamonten board but the version on it is v2012.04 but I came to know that v2012.10 or v2013.01 supports the Tamontenboard through some guys here..
It would be great if you can tell me how can I accomplish v2013.01 or v2012.10 into the build system and make it available so that I can compile the and get uImage
(Tamonten board is a derivative of harmony board with some changes and has arm cortexa9 processor without neon extentions )
I am kind of new to add new .bb files and help is really appreciated as I am not able to figure out how to add
Greetings & Regards, Swaroop
|
|
|
Re: Avionic Tamonten Board - Uboot problem
On 2013-02-20 00:21, Satya Swaroop Damarla wrote: Hi Gary,
I think you are right that we need may be the new uboot version but it is not available in the uboot directory of the poky and i get the follwoing warning and the simulation is
ending like previously....
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version v2013.01% of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: v2011.03+git26+19b54a701811220221fc4d5089a2bb18892018ca v2011.06+git27+b1af6f532e0d348b153d5c148369229d24af361a
v2012.04.01+git25+415d386877df49eb051b85ef74fa59a16dc17c7d
NOTE: preferred version v2013.01% of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: v2011.03+git26+19b54a701811220221fc4d5089a2bb18892018ca v2011.06+git27+b1af6f532e0d348b153d5c148369229d24af361a
v2012.04.01+git25+415d386877df49eb051b85ef74fa59a16dc17c7d
NOTE: preferred version v2013.01% of u-boot not available (for item u-boot-dev)
NOTE: versions of u-boot available: v2011.03+git26+19b54a701811220221fc4d5089a2bb18892018ca v2011.06+git27+b1af6f532e0d348b153d5c148369229d24af361a
v2012.04.01+git25+415d386877df49eb051b85ef74fa59a16dc17c7d
May be you can tell me how to add the new uboot file The easiest way is to just add the meta-ti layer - they have a recipe for 2013.01. n.b. It's common courtesy to keep such discussions on the mailing list so that everyone benefits from the answers. On Tue, Feb 19, 2013 at 7:36 PM, Gary Thomas <gary@... <mailto:gary@...>> wrote:
On 2013-02-19 09:02, Satya Swaroop Damarla wrote:
Unfortunately "tec_config" didnot work. Here is the error message
I think you need a newer U-Boot to get the support for this board.
Try
PREFERRED_VERSION_u-boot ?= "v2012.10%"
or even
PREFERRED_VERSION_u-boot ?= "v2013.01%"
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 8 CROSS_COMPILE=arm-poky-linux-__gnueabi- CC=arm-poky-linux-gnueabi-gcc --sysroot=/home/build/yocto/__poky/buildTamonten/tmp/__sysroots/skidata-tamonten
tec_config
| make: *** No rule to make target `tec_config'. Stop.
| make: *** [tec_config] Error 1
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see
/home/build/yocto/poky/__buildTamonten/tmp/work/__skidata_tamonten-poky-linux-__gnueabi/u-boot-v2012.04.01+__git3+__415d386877df49eb051b85ef74fa59__a16dc17c7d-r2/temp/log.do___compile.21665
for
further information)
ERROR: Task 69 (/home/build/yocto/poky/meta/__recipes-bsp/u-boot/u-boot___2012.04.01.bb <http://u-boot_2012.04.01.bb> <http://u-boot_2012.04.01.bb>, do_compile) failed with
exit code '1'
NOTE: Tasks Summary: Attempted 3421 tasks of which 319 didn't need to be rerun and 1 failed.
On Tue, Feb 19, 2013 at 3:58 PM, Gary Thomas <gary@... <mailto:gary@...> <mailto:gary@... <mailto:gary@...>>> wrote:
On 2013-02-19 06:28, Satya Swaroop Damarla wrote:
Hi,
I want to build a basic image for the Avionic Tamonten board using Yocto. SO, I created a skidata-tamonten.conf in the list of machines based on the
beagleboard.conf but I dont
know what to add for the UBOOT_MACHINE= . I tried my best to use the same "omap_beagle_conf" but it doesnot boot properly. Here is the skidata-tamonten.conf file
description
Try 'tec_config'
#@TYPE: Machine
#@NAME: skidata-tamonten machine
#@DESCRIPTION: Machine configuration for the Tamonten board
PREFERRED_PROVIDER_virtual/____xserver ?= "xserver-xorg"
XSERVER ?= "xserver-xorg \
xf86-input-evdev \
xf86-input-mouse \
xf86-video-omapfb \
xf86-input-keyboard"
# Ship all kernel modules by default
MACHINE_EXTRA_RRECOMMENDS = " kernel-modules"
# Allow for MMC booting ()
EXTRA_IMAGEDEPENDS += "u-boot"
# Uncomment the following line to enable the hard floating point abi. Note that
# this breaks some binary libraries and 3D (neither of which ship with
# meta-yocto). For maximum compatibility, leave this disabled.
DEFAULTTUNE ?= "cortexa9thf"
include conf/machine/include/tune-____cortexa9.inc
IMAGE_FSTYPES += "tar.bz2 ext2 ext3"
SERIAL_CONSOLE = "115200 ttyO2"
PREFERRED_PROVIDER_virtual/____kernel ?= "linux-yocto"
PREFERRED_VERSION_linux-yocto ?= "3.2%"
KERNEL_IMAGETYPE = "uImage"
PREFERRED_VERSION_u-boot ?= "v2012.04%"
UBOOT_MACHINE = "???????????????????"
UBOOT_ENTRYPOINT = "0x00008000"
UBOOT_LOADADDRESS = "0x00008000"
MACHINE_FEATURES = "usbgadget usbhost vfat alsa screen touchscreen keyboard"
Greetings & Regards,
Swaroop
___________________________________________________
yocto mailing list
yocto@... <mailto:yocto@...> <mailto:yocto@... <mailto:yocto@...>__>
https://lists.yoctoproject.____org/listinfo/yocto <https://lists.yoctoproject.__org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>>
--
------------------------------____----------------------------__--
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------____----------------------------__--
___________________________________________________
yocto mailing list
yocto@... <mailto:yocto@...> <mailto:yocto@... <mailto:yocto@...>__>
https://lists.yoctoproject.____org/listinfo/yocto <https://lists.yoctoproject.__org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>>
--
------------------------------__------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------__------------------------------
-- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
|
|
|
On Tue, 2013-02-19 at 21:01 -0800, Flanagan, Elizabeth wrote: I'm currently at ELC and am going to be a little slow with email.
However, tonight I will be building M4 rc1. We are looking pretty
green and had been hoping to use the last build for rc1, but we want
to get it a little closer as to have it all green. I will be building
it from current master head and will branch/tag in the morning. If you
maintain a layer that I don't have branch access for, please create
the milestone branch for it from the git hashes I send out in the
morning. Thanks. We continued to have a build issue which I traced back to the recent bitbake fetcher changes. I've reverted a part of that and rebuilt master and its looking even better than the previous build, lots of green. I think we'll therefore be going with that revision (7d22ef28e64de06b6238d0ef9b664c0bee6efa46) for M4-rc1, assuming the rest builds out ok. Cheers, Richard
|
|
|
Re: [PATCH] meta: Search also FILESEXTRAPATHS for systemd service files
Burton, Ross <ross.burton@...>
Hi,
First, mails that patch oe-core should be sent to the oe-core list,
not yocto@ (which is more of a support channel).
Second this patch won't do what you expect - when you find a file in
FILESEXTRAPATHS it isn't being installed, so it won't be in the
package.
I intentionally removed code that did something similar from the
original systemd.bbclass as generally a service file will have to be
processed in some way to put the right paths in: hardcoding
/usr/sbin/some-daemon isn't sufficient when the distribution can
change the value of $sbindir.
Ross
|
|
|
[PATCH] meta: Search also FILESEXTRAPATHS for systemd service files
Jukka Rissanen <jukka.rissanen@...>
Signed-off-by: Jukka Rissanen <jukka.rissanen@...>
---
meta/classes/systemd.bbclass | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/meta/classes/systemd.bbclass b/meta/classes/systemd.bbclass
index 564cd72..b807d4e 100644
--- a/meta/classes/systemd.bbclass
+++ b/meta/classes/systemd.bbclass
@@ -1,3 +1,5 @@
+inherit utils
+
# The list of packages that should have systemd packaging scripts added. For
# each entry, optionally have a SYSTEMD_SERVICE_[package] that lists the service
# files in this package. If this variable isn't set, [package].service is used.
@@ -137,6 +139,7 @@ python systemd_populate_packages() {
# single service gets also the /dev/null dummies
keys = 'Also Conflicts'
# scan for all in SYSTEMD_SERVICE[]
+ extrapaths = base_set_filespath([],d).split(":")
for pkg_systemd in systemd_packages.split():
for service in get_package_var(d, 'SYSTEMD_SERVICE', pkg_systemd).split():
path_found = ''
@@ -144,6 +147,11 @@ python systemd_populate_packages() {
if os.path.exists(oe.path.join(d.getVar("D", True), path, service)):
path_found = path
break
+ if path_found == '':
+ for path in extrapaths:
+ if os.path.exists(oe.path.join(path, service)):
+ path_found = path
+ break
if path_found != '':
systemd_add_files_and_parse(pkg_systemd, path_found, service, keys)
else:
--
1.7.11.4
|
|
|
Re: [PATCH] meta: Fix error print
Burton, Ross <ross.burton@...>
On 20 February 2013 11:15, Jukka Rissanen <jukka.rissanen@...> wrote: - bb.error('%s does not appear in package list, please add it', " " + pkg_systemd)
+ bb.error('%s does not appear in package list, please add it' % pkg_systemd) Whoops. Acked-by: Ross Burton <ross.burton@...> Ross
|
|
|
Re: [meta-raspberrypi][PATCH 1/1] rpi-first-run-wizard: Fix RDEPENDS warning
toggle quoted message
Show quoted text
On Tue, Feb 19, 2013 at 4:03 PM, Philipp Wagner <lists@...> wrote:
Am 10.02.2013 18:55, schrieb Andrei Gherzan:
WARNING: QA Issue: [...]/rpi-first-run-wizard.bb:
Variable RDEPENDS is set as not being package specific, please fix this.
Signed-off-by: Andrei Gherzan <andrei@...>
---
recipes-extra/startup/rpi-first-run-wizard.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-extra/startup/rpi-first-run-wizard.bb b/recipes-extra/startup/rpi-first-run-wizard.bb
index c5cef7c..6ede56e 100644
--- a/recipes-extra/startup/rpi-first-run-wizard.bb
+++ b/recipes-extra/startup/rpi-first-run-wizard.bb
@@ -3,11 +3,11 @@ LICENSE = "GPLV2"
LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
DEPENDS = "zenity dbus"
-RDEPENDS = "slim sudo zenity dbus"
+RDEPENDS_${PN} = "slim sudo zenity dbus"
COMPATIBLE_MACHINE = "raspberrypi"
-PR = "r1"
+PR = "r2"
SRC_URI = " \
file://LICENSE \
Philipp
--
Andrei Gherzan
m: +40.744.478.414 | f: +40.31.816.28.12
|
|
|
Re: [meta-raspberrypi][PATCH 1/7] rpi-default-providers: Remove virtual/libgl provider
Thank you. You hint is OK and will apply patches with your suggestion.
Thanks.
On Tue, Feb 19, 2013 at 4:11 PM, Philipp Wagner <lists@...> wrote:
Hi Andrei,
I applied and tested all 7 patches and they work as the binary firmware did before. Maybe in a later patch a pkgconfig file can be added (I think it was there before, but I'm not using it yet, so I'm not really sure).
I don't like the name "userland" (it's not really describing that we're actually talking about graphics libraries), but that's just a nitpick. Maybe it can be renamed to rpi-graphics-userland or something more descriptive like that?
Philipp
Am 09.02.2013 23:11, schrieb Andrei Gherzan:
There are no libgl binary shipped in raspberrypi firmware repo.
Signed-off-by: Andrei Gherzan <andrei@...>
---
conf/machine/include/rpi-default-providers.inc | 1 -
1 file changed, 1 deletion(-)
diff --git a/conf/machine/include/rpi-default-providers.inc b/conf/machine/include/rpi-default-providers.inc
index ce963b3..6abab60 100644
--- a/conf/machine/include/rpi-default-providers.inc
+++ b/conf/machine/include/rpi-default-providers.inc
@@ -4,5 +4,4 @@ PREFERRED_PROVIDER_virtual/kernel = "linux-raspberrypi"
PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
PREFERRED_PROVIDER_virtual/egl ?= "vc-graphics-hardfp"
PREFERRED_PROVIDER_virtual/libgles2 ?= "vc-graphics-hardfp"
-PREFERRED_PROVIDER_virtual/libgl ?= "vc-graphics-hardfp"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-raspberrypi"
--
Andrei Gherzan
m: +40.744.478.414 | f: +40.31.816.28.12
|
|
|
[PATCH] meta: Fix error print
Jukka Rissanen <jukka.rissanen@...>
Instead of printing
ERROR: %s does not appear in package list, please add it package-systemd
print
ERROR: package-systemd does not appear in package list, please add it
instead.
Signed-off-by: Jukka Rissanen <jukka.rissanen@...>
---
meta/classes/systemd.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/systemd.bbclass b/meta/classes/systemd.bbclass
index 00865ed..564cd72 100644
--- a/meta/classes/systemd.bbclass
+++ b/meta/classes/systemd.bbclass
@@ -53,7 +53,7 @@ python systemd_populate_packages() {
def systemd_check_package(pkg_systemd):
packages = d.getVar('PACKAGES', True)
if not pkg_systemd in packages.split():
- bb.error('%s does not appear in package list, please add it', " " + pkg_systemd)
+ bb.error('%s does not appear in package list, please add it' % pkg_systemd)
# Add a runtime dependency on systemd to pkg
--
1.7.11.4
|
|
|
