date:20161002

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

2016-10-02 Thread Gary Thomas


On 2016-10-02 17:58, Karim ATIKI wrote:

Hi Gary,



That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02

Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.



I've cloned meta-raspberrypi and meta-openembedded with the latest branches.

It still fails at the same step ☹ (see below).


The key is that you must use the latest OE-core (or Poky/Yocto) layer.




I'm building a custom core-image-x11 for my raspberrypi3 board, with poky 
krogoth.

In the very last steps:


ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Function failed: 
do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)


ERROR: Logfile of failure stored in:

/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110


Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_rpi_sdimg
| Creating filesystem with Boot partition 40960 KiB and RootFS 430080 KiB

| dd: failed to open 
'/core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
denied

| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)

ERROR: Task 16 
(/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb, 
do_image_rpi_sdimg) failed
with exit code '1'
NOTE: Tasks Summary: Attempted 4771 tasks of which 4770 didn't need to be rerun 
and 1 failed.
No currently running tasks (4367 of 4773)


It looks like it tries to create the image in the path:
  /core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
denied


I looked into the bbclass, and at first glance I'd say that the respective path
is "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"


So ${IMGDEPLOYDIR} seems to be empty.


I haven't found any reference to IMGDEPLOYDIR elsewhere.



Make sure you have the latest [master] revisions.  This should have been fixed 
by:

commit 4817e2c087097c02755d6309304878e42cf61d3c
Author: Andreas Müller 
Date:   Tue Sep 13 02:19:06 2016 +0200

sdcard_image-rpi.bbclass: avoid corrupted images with latest oe-core



That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02

Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.



--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Recipe reporting system] Upgradable recipe name list

2016-10-02 Thread recipe-report

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   VersionUpstream version  Maintainer  
NoUpgradeReason
  -    --  
--
liberation-fonts  1.04   2.00.1Alexander Kanavin   
2.x depends on fontforge pa...
gobject-introspec...  1.48.0 1.50.0Alexander Kanavin
boost 1.61.0 1.62.0Alexander Kanavin
openssl   1.0.2j 1.1.0bAlexander Kanavin
gnome-desktop33.20.2 3.22.0Alexander Kanavin
gnutls3.5.3  3.5.4 Alexander Kanavin
vala  0.32.1 0.34.0Alexander Kanavin
bjam-native   1.61.0 1.62.0Alexander Kanavin
nspr  4.12   4.13  Alexander Kanavin
nss   3.25   3.26  Alexander Kanavin
webkitgtk 2.12.5 2.14.0Alexander Kanavin
ffmpeg3.1.3  3.1.4 Alexander Kanavin
dtc   1.4.1+gitX 1.4.2+gitAUTOINC+...  Alexander Kanavin
kexec-tools   2.0.12 2.0.13Alexander Kanavin
epiphany  3.20.3 3.22.0Alexander Kanavin
sysprof   3.20.0+gitX3.22.0+gitAUTOINC...  Alexander Kanavin
cmake-native  3.6.1  3.6.2 Alexander Kanavin
btrfs-tools   4.7.1  4.7.3 Alexander Kanavin
mpg1231.23.6 1.23.8Alexander Kanavin
cmake 3.6.1  3.6.2 Alexander Kanavin
mkelfimage4.0+gitX   4.4+gitAUTOINC+58...  Alexander Kanavin   
mkelfimage has been removed...
libksba   1.3.4  1.3.5 Alexander Kanavin
perl  5.22.1 5.24.1Aníbal Limón
apt   1.2.12 1.3   Aníbal Limón
apt-native1.2.12 1.3   Aníbal Limón
dpkg  1.18.7 1.18.10   Aníbal Limón
perl-native   5.22.1 5.24.1Aníbal Limón
pinentry  0.9.2  0.9.7 Armin Kuster
nettle3.23.3   Armin Kuster
linux-libc-headers4.8-rc48 Bruce Ashfield
guilt-native  0.35+gitX  0.36+gitAUTOINC+2...  Bruce Ashfield
cups  2.1.4  2.2.0 Chen Qi
curl  7.50.1 7.50.3Chen Qi
systemd-boot  230+gitX   231+gitAUTOINC+38...  Chen Qi
dbus-glib 0.106  0.108 Chen Qi
gawk  4.1.3  4.1.4 Chen Qi
systemd   230+gitX   231+gitAUTOINC+38...  Chen Qi
util-linux2.28.1 2.28.2Chen Qi
sudo  1.8.17p1   1.8.18Chen Qi
sysstat   11.4.0 11.5.1Chen Qi
systemd-bootchart 230+gitX   231+gitAUTOINC+9e...  Chen Qi
diffutils 3.43.5   Chen Qi
grep  2.25   2.26  Chen Qi
build-appliance-i...  15.0.0 15.0.1Cristian Iorga
docbook-sgml-dtd-...  3.13.1">3.1/

Re: [yocto] [prelink-cross] Support x32 libx32 directory

2016-10-02 Thread Mark Hatle

On 10/2/16 6:18 PM, Khem Raj wrote:
> Mark
> 
> have we integrated this patch ?

I have not yet.  Continue to ping me, I should hopefully get to it this week.

--Mark

>> On Sep 14, 2016, at 4:23 PM, Joseph Myers  wrote:
>>
>> Cross-prelink's prelink-rtld is missing suport for the /libx32
>> directory used with the x86_64 x32 ABI.  This patch adds such support.
>>
>> 2016-09-14  Joseph Myers  
>>
>>  * src/rtld/rtld.c (load_ld_so_conf): Add argument use_x32.
>>  (main): Update call to load_ld_so_conf.
>>
>> diff --git a/src/rtld/rtld.c b/src/rtld/rtld.c
>> index 8d7d760..2d72083 100644
>> --- a/src/rtld/rtld.c
>> +++ b/src/rtld/rtld.c
>> @@ -409,7 +409,7 @@ free_path (struct search_path *path)
>> }
>>
>> void
>> -load_ld_so_conf (int use_64bit, int use_mipsn32)
>> +load_ld_so_conf (int use_64bit, int use_mipsn32, int use_x32)
>> {
>>   int fd;
>>   FILE *conf;
>> @@ -435,6 +435,14 @@ load_ld_so_conf (int use_64bit, int use_mipsn32)
>>   add_dir (_dirs, "/usr/lib32/tls", strlen ("/usr/lib32/tls"));
>>   add_dir (_dirs, "/usr/lib32", strlen ("/usr/lib32"));
>> }
>> +  else if (use_x32)
>> +{
>> +  dst_LIB = "libx32";
>> +  add_dir (_dirs, "/libx32/tls", strlen ("/libx32/tls"));
>> +  add_dir (_dirs, "/libx32", strlen ("/libx32"));
>> +  add_dir (_dirs, "/usr/libx32/tls", strlen ("/usr/libx32/tls"));
>> +  add_dir (_dirs, "/usr/libx32", strlen ("/usr/libx32"));
>> +}
>>   else
>> {
>>   dst_LIB = "lib";
>> @@ -1195,7 +1203,8 @@ main(int argc, char **argv)
>>  }
>>
>>   load_ld_so_conf (gelf_getclass (dso->elf) == ELFCLASS64,
>> -( dso->ehdr.e_machine == EM_MIPS) && ( dso->ehdr.e_flags & 
>> EF_MIPS_ABI2 ) );
>> +( dso->ehdr.e_machine == EM_MIPS) && ( dso->ehdr.e_flags & 
>> EF_MIPS_ABI2 ),
>> +dso->ehdr.e_machine == EM_X86_64 && gelf_getclass (dso->elf) == 
>> ELFCLASS32);
>>
>>   if (multiple)
>>  printf ("%s:\n", argv[remaining]);
>>
>> --
>> Joseph S. Myers
>> jos...@codesourcery.com
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] taskhash mismatch

2016-10-02 Thread Khem Raj


> On Oct 2, 2016, at 7:34 AM, Trevor Woerner <twoer...@gmail.com> wrote:
> 
> Hi,
> 
> For the last week or so my raspberry pi builds have been failing with:
> 
> ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 
> 2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for 
> /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
> ERROR: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus 
> a47bfc12fdfa29c58fe72cf8e0a28e91 for 
> /z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
> 
> This is with both poky and oe+bitbake, master branches all around, and fully
> up-to-date. Before sending this email I pulled yet again and re-tested just to
> confirm.
> 

is it due to use of DATE and TIME issue ? I think there was such a patch 
proposed to meta-rpi see
http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=4c02c7ce07121c2f5367204445f93199d828bb10

> Poky:
> 
>   Build Configuration:
>   BB_VERSION= "1.31.1"
>   BUILD_SYS = "x86_64-linux"
>   NATIVELSBSTRING   = "SUSELINUX-42.1"
>   TARGET_SYS= "arm-poky-linux-gnueabi"
>   MACHINE   = "raspberrypi"
>   DISTRO= "poky"
>   DISTRO_VERSION= "2.1+snapshot-20161002"
>   TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
>   TARGET_FPU= "hard"
>   meta
>   meta-poky = "master:3a73fe0efcb7aeefcca7011bba887caad03d4d03"
>   meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
> 
> OE + bitbake:
> 
>   Build Configuration:
>   BB_VERSION= "1.31.1"
>   BUILD_SYS = "x86_64-linux"
>   NATIVELSBSTRING   = "SUSELINUX-42.1"
>   TARGET_SYS= "arm-oe-linux-gnueabi"
>   MACHINE   = "raspberrypi"
>   DISTRO= "nodistro"
>   DISTRO_VERSION= "nodistro.0"
>   TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
>   TARGET_FPU= "hard"
>   meta  = "master:21cc2a3f63ea260dbf6b50e2fd4dd50cacdd9935"
>   meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to build an SDK toolchain for native x86_64

2016-10-02 Thread Khem Raj


> On Sep 15, 2016, at 10:04 PM, Josias Inacio da Silva Filho 
>  wrote:
> 
> Hi folks,
> 
> Here’s my current setup and current situation:
> 
> Host: x86_64
> Target: aarch64
> 
> Build core-image-base for aarch64 - OK
> populate_sdk for aarch64 - OK
> 
> My application and it unit tests also gets compiled to aarch64.
> 
> What I wanted now would be something like run populate_sdk for 
> “core-image-base-native”. The reason for that is because I want to compile 
> and run my unit tests using my host machine only (x86_64). This makes 
> application development much easier, since I don’t need the target nor QEMU 
> to run the unit tests. And I still want the toolchain to be generated by 
> Yocto since it solves all package dependencies for me.
> 
> What I attempted:
> 
> 1) Create a new “core-image-toolchain-native” similar to core-image-base, but 
> tweaking to be able to build for native. That does not seem to be the right 
> way, I spent a lot of time doing this and got nowhere since many of the 
> image's recipes do not support building with native support.
> 
> 2) Change my machine type to be qemux86_64, then call “bitbake 
> core-image-base -c populate_sdk”. That would generate a toolchain for x86-64 
> right? Well it did, and I was able to use this toolchain to compile my unit 
> tests for x86_64. But the problem is that this still assumes that I’ll be 
> running those unit tests on the target machine ( QEMU x86_64), so if I try to 
> run it in my host machine, it complains about some missing dynamic libraries 
> that are only found in the sysroot of the target qemux86_64.
> 
> Is there any proper solution for this case?

This is not a usecase which SDK is meant for, the SDK is generally meant for 
doing cross development as you have also
seen above, and why the native case it not covered is also due to fact you 
explained above where you see some missing
libraries. Can this be fixed, sure it can, but its a new feature that would 
require additional considerations if we
have to provide SDK host and cross SDK, this may have usecases but its not so 
common.

Ideally, you should use the gcc toolchain as installed on your SDK host ( one 
from ubuntu/debian/fedora whatever distro you use )
and use that for native verification.

You are welcome to file an enhancement request in bugzilla for SDK support for 
SDK host.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] Support x32 libx32 directory

2016-10-02 Thread Khem Raj

Mark

have we integrated this patch ?

> On Sep 14, 2016, at 4:23 PM, Joseph Myers  wrote:
> 
> Cross-prelink's prelink-rtld is missing suport for the /libx32
> directory used with the x86_64 x32 ABI.  This patch adds such support.
> 
> 2016-09-14  Joseph Myers  
> 
>   * src/rtld/rtld.c (load_ld_so_conf): Add argument use_x32.
>   (main): Update call to load_ld_so_conf.
> 
> diff --git a/src/rtld/rtld.c b/src/rtld/rtld.c
> index 8d7d760..2d72083 100644
> --- a/src/rtld/rtld.c
> +++ b/src/rtld/rtld.c
> @@ -409,7 +409,7 @@ free_path (struct search_path *path)
> }
> 
> void
> -load_ld_so_conf (int use_64bit, int use_mipsn32)
> +load_ld_so_conf (int use_64bit, int use_mipsn32, int use_x32)
> {
>   int fd;
>   FILE *conf;
> @@ -435,6 +435,14 @@ load_ld_so_conf (int use_64bit, int use_mipsn32)
>   add_dir (_dirs, "/usr/lib32/tls", strlen ("/usr/lib32/tls"));
>   add_dir (_dirs, "/usr/lib32", strlen ("/usr/lib32"));
> }
> +  else if (use_x32)
> +{
> +  dst_LIB = "libx32";
> +  add_dir (_dirs, "/libx32/tls", strlen ("/libx32/tls"));
> +  add_dir (_dirs, "/libx32", strlen ("/libx32"));
> +  add_dir (_dirs, "/usr/libx32/tls", strlen ("/usr/libx32/tls"));
> +  add_dir (_dirs, "/usr/libx32", strlen ("/usr/libx32"));
> +}
>   else
> {
>   dst_LIB = "lib";
> @@ -1195,7 +1203,8 @@ main(int argc, char **argv)
>   }
> 
>   load_ld_so_conf (gelf_getclass (dso->elf) == ELFCLASS64,
> - ( dso->ehdr.e_machine == EM_MIPS) && ( dso->ehdr.e_flags & 
> EF_MIPS_ABI2 ) );
> + ( dso->ehdr.e_machine == EM_MIPS) && ( dso->ehdr.e_flags & 
> EF_MIPS_ABI2 ),
> + dso->ehdr.e_machine == EM_X86_64 && gelf_getclass (dso->elf) == 
> ELFCLASS32);
> 
>   if (multiple)
>   printf ("%s:\n", argv[remaining]);
> 
> --
> Joseph S. Myers
> jos...@codesourcery.com
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding mysql in bitbaking meta-toolchain-qt5

2016-10-02 Thread Khem Raj


> On Sep 14, 2016, at 12:54 AM, amb...@iwavesystems.com wrote:
> 
> 
> Hello,
> 
> I’m doing bitbake of meta-toolchain-qt5. When trying to use mysql, not able 
> to find it in include/ directory.
> 
> mysql sources is located in the below path in my yocto setup,
> 
> sources/meta-openembedded/meta-oe/recipes-support/mysql
> 
> Tried to include mysql by adding the below to conf/local.conf under build 
> directory but could not able to locate mysql under include/.
> (Also not sure whether I’m doing it right.)
> 
> IMAGE_INSTALL_append = ”mysql”

if you are not using populate_sdk task to generate SDK then this wont be 
sufficient you have to append it to
TOOLCHAIN_TARGET_TASK

> 
> Can anyone please let me know the procedure to include mysql to the 
> meta-toolchain-qt5.
> 
> Thanks in Advance.
> 
> Regards,
> Ambika.
> 
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

2016-10-02 Thread Nicolas ADELL

Hi Karim and Gary,

I have had the same problem this afternoon by trying to build the 
rpi-base-image for my raspberrypi board, with poky Krogoth.

The oe-core repo (openembedded-core branch krogoth) has been fetched, but I 
still get the error while building the image.

However, I didn't find the commit 6d969bacc718e21a5246d4da9bf9639dcae29b02.
Could you give any other informations ?


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

2016-10-02 Thread Karim ATIKI

Hi Gary,


>That said, you also need a recent checkout of OE-core as the meta-raspberrypi
>and OE-core layers need to be in sync. These particular variables were changed
>starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02
>
>Just use the latest master of both meta-raspberrypi and OE-core
>and you should be fine.


I've cloned meta-raspberrypi and meta-openembedded with the latest branches.

It still fails at the same step [☹]  (see below).


Karim

>>
>>
>> I'm building a custom core-image-x11 for my raspberrypi3 board, with poky 
>> krogoth.
>>
>> In the very last steps:
>>
>>
>> ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Function failed: 
>> do_image_rpi_sdimg (log file is located at
>> /home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)
>>
>>
>> ERROR: Logfile of failure stored in:
>>
>> /home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110
>>
>>
>> Log data follows:
>> | DEBUG: Executing python function set_image_size
>> | DEBUG: Python function set_image_size finished
>> | DEBUG: Executing shell function do_image_rpi_sdimg
>> | Creating filesystem with Boot partition 40960 KiB and RootFS 430080 KiB
>>
>> | dd: failed to open 
>> '/core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
>> denied
>>
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_image_rpi_sdimg (log file is located at
>> /home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)
>>
>> ERROR: Task 16 
>> (/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb,
>>  do_image_rpi_sdimg) failed
>> with exit code '1'
>> NOTE: Tasks Summary: Attempted 4771 tasks of which 4770 didn't need to be 
>> rerun and 1 failed.
>> No currently running tasks (4367 of 4773)
>>
>>
>> It looks like it tries to create the image in the path:
>>   /core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
>> denied
>>
>>
>> I looked into the bbclass, and at first glance I'd say that the respective 
>> path
>> is "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
>>
>>
>> So ${IMGDEPLOYDIR} seems to be empty.
>>
>>
>> I haven't found any reference to IMGDEPLOYDIR elsewhere.
>>
>
> Make sure you have the latest [master] revisions.  This should have been 
> fixed by:
>
> commit 4817e2c087097c02755d6309304878e42cf61d3c
> Author: Andreas Müller 
> Date:   Tue Sep 13 02:19:06 2016 +0200
>
> sdcard_image-rpi.bbclass: avoid corrupted images with latest oe-core
>

That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02

Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
yocto -- Discussion of all things Yocto 
Project
lists.yoctoproject.org
Discussion of all things about the Yocto Project. Read our Community Guidelines 
or learn more about how to participate in other community discussions.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi] taskhash mismatch

2016-10-02 Thread Trevor Woerner

Hi,

For the last week or so my raspberry pi builds have been failing with:

ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 
2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for 
/z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
ERROR: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus 
a47bfc12fdfa29c58fe72cf8e0a28e91 for 
/z/raspi2/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg

This is with both poky and oe+bitbake, master branches all around, and fully
up-to-date. Before sending this email I pulled yet again and re-tested just to
confirm.

Poky:

Build Configuration:
BB_VERSION= "1.31.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "SUSELINUX-42.1"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi"
DISTRO= "poky"
DISTRO_VERSION= "2.1+snapshot-20161002"
TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
TARGET_FPU= "hard"
meta
meta-poky = "master:3a73fe0efcb7aeefcca7011bba887caad03d4d03"
meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"

OE + bitbake:

Build Configuration:
BB_VERSION= "1.31.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "SUSELINUX-42.1"
TARGET_SYS= "arm-oe-linux-gnueabi"
MACHINE   = "raspberrypi"
DISTRO= "nodistro"
DISTRO_VERSION= "nodistro.0"
TUNE_FEATURES = "arm armv6  vfp arm1176jzfs callconvention-hard"
TARGET_FPU= "hard"
meta  = "master:21cc2a3f63ea260dbf6b50e2fd4dd50cacdd9935"
meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

2016-10-02 Thread Gary Thomas


On 2016-10-02 06:52, Gary Thomas wrote:

On 2016-10-01 15:58, Karim ATIKI wrote:

hi,


I'm building a custom core-image-x11 for my raspberrypi3 board, with poky 
krogoth.

In the very last steps:


ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Function failed: 
do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)


ERROR: Logfile of failure stored in:

/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110


Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_rpi_sdimg
| Creating filesystem with Boot partition 40960 KiB and RootFS 430080 KiB

| dd: failed to open 
'/core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
denied

| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)

ERROR: Task 16 
(/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb, 
do_image_rpi_sdimg) failed
with exit code '1'
NOTE: Tasks Summary: Attempted 4771 tasks of which 4770 didn't need to be rerun 
and 1 failed.
No currently running tasks (4367 of 4773)


It looks like it tries to create the image in the path:
  /core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission 
denied


I looked into the bbclass, and at first glance I'd say that the respective path
is "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"


So ${IMGDEPLOYDIR} seems to be empty.


I haven't found any reference to IMGDEPLOYDIR elsewhere.



Make sure you have the latest [master] revisions.  This should have been fixed 
by:

commit 4817e2c087097c02755d6309304878e42cf61d3c
Author: Andreas Müller 
Date:   Tue Sep 13 02:19:06 2016 +0200

sdcard_image-rpi.bbclass: avoid corrupted images with latest oe-core



That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02

Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

[yocto] [Recipe reporting system] Upgradable recipe name list

Re: [yocto] [prelink-cross] Support x32 libx32 directory

Re: [yocto] [meta-raspberrypi] taskhash mismatch

Re: [yocto] How to build an SDK toolchain for native x86_64

Re: [yocto] [prelink-cross] Support x32 libx32 directory

Re: [yocto] Adding mysql in bitbaking meta-toolchain-qt5

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

[yocto] [meta-raspberrypi] taskhash mismatch

Re: [yocto] [meta-raspberrypi] failed to copy the final ***rootfs.rpi-sdimg image file

11 matches

Site Navigation

Mail list logo

Footer information