**** BEGIN LOGGING AT Mon Mar 12 03:00:01 2018
Mar 12 06:03:08 <yocti> New news from stackoverflow: Yocto project cannot find asm/errno.h <https://stackoverflow.com/questions/49228933/yocto-project-cannot-find-asm-errno-h>
Mar 12 07:22:51 <phako[m]> hm, seems to be fixed with 0.44.1
Mar 12 08:08:28 <phako[m]> whoops wrong chat
Mar 12 08:12:21 <lukma> Dear All,
Mar 12 08:12:23 <lukma> If I want to add package foo to SDK, then I extend either TOOLCHAIN_HOST_TASK_append = " foo" or make a bbappend to nativesdk-packagegroup-sdk-host's
Mar 12 08:12:23 <lukma> RDEPENDS_${PN} += " native foo"
Mar 12 08:12:23 <lukma> This works for SDK.
Mar 12 08:12:39 <lukma> But how to make the same for eSDK ?
Mar 12 08:12:39 <lukma> I've added: TOOLCHAIN_HOST_TASK_append = " nativesdk-foo"
Mar 12 08:12:39 <lukma> But then I do see following error after installing sysroot:
Mar 12 08:12:39 <lukma> foo
Mar 12 08:12:39 <lukma>  -bash: /opt/ccc/sysroots/x86_64-pokysdk-linux/usr/bin/foo: No such file or directory
Mar 12 08:12:40 <lukma> file foo
Mar 12 08:12:40 <lukma> /opt/ccc/sysroots/x86_64-pokysdk-linux/usr/bin/file: line 4: /opt/ccc/sysroots/x86_64-pokysdk-linux/usr/bin/file.real: No such file or directory
Mar 12 08:12:41 <lukma> What is the purpose of "file.real"?
Mar 12 08:12:41 <lukma> I would expect to have the binary installed in eSDK, as it is done in SDK.
Mar 12 08:12:42 <lukma> I've double check and: SDK_INCLUDE_TOOLCHAIN = “1” - so we shall install in eSDK the same set of binaries
Mar 12 08:12:42 <lukma> as we did with SDK - or do I mis something?
Mar 12 08:13:31 <lukma> The problem is that nativesdk packages are bundled into SDK, but show above error for eSDK.
Mar 12 12:32:49 <dzen> well, I'm confused. I' trying to create some recipe that creates python wheels out of some python code. The wheel are note built using the desired target : it's x86-64 and not arm:
Mar 12 12:32:52 <dzen> psutil-5.4.3-cp35-cp35m-linux_x86_64.whl
Mar 12 12:33:12 <dzen> Is there any hint to be sure to use the correct toolchain to build it ?
Mar 12 13:02:33 <rburton> dzen: its possibly hardcoding the user of 'gcc' and not $CC
Mar 12 13:16:36 <dzen> rburton: aww
Mar 12 13:19:29 <dzen> rburton: not only. seems when I call "python" in my recipe, it uses python 3.5 amd64
Mar 12 13:19:42 <rburton> well yes, you can't run the target python can you
Mar 12 13:20:01 <rburton> if the wheel generation is using the arch of the py its running in then yes that will break
Mar 12 13:22:33 <dzen> any chance to run the target python version ? would be very helpfull
Mar 12 13:30:24 <rburton> dzen: would be easier to fix the cross-compilation problem in wheels properly
Mar 12 13:33:44 <dzen> imho it's correctly done : https://github.com/giampaolo/psutil/blob/master/setup.py
Mar 12 13:52:29 <dzen> well I have to read the setuptools / distutils recipes
Mar 12 13:59:35 <lukma> Can somebody correct my understanding:
Mar 12 13:59:54 <lukma> TOOLCHAIN_HOST_TASK="nativesdk-packagegroup-sdk-host packagegroup-cross-canadian-qemu nativesdk-XXX"
Mar 12 14:00:08 <lukma> Is the TOOLCHAIN_HOST_TASK for SDK (-c populate_sdk)
Mar 12 14:00:15 <lukma> on the other hand
Mar 12 14:00:36 <lukma> TOOLCHAIN_HOST_TASK_task-populate-sdk-ext="     meta-environment-extsdk-qemu     "
Mar 12 14:00:57 <lukma> is for eSDK - > which shall have the former included (or add its tools) ?
Mar 12 14:01:26 <lukma> In other words - if SDK_INCLUDE_TOOLCHAIN = “1”
Mar 12 14:01:57 <lukma> then -c populate_sdk_ext will consist of elements from TOOLCHAIN_HOST_TASK and TOOLCHAIN_HOST_TASK_task-populate-sdk-ext
Mar 12 14:02:00 <lukma> is this correct ?
Mar 12 16:12:03 <jose__> Hi, I have build ROCKO images for beaglebone but I'm unable to boot from my SD, my boot partition contains MLO and u-boot.img "/dev/sde1  *      2048   147455   145408   71M  c W95 FAT32 (LBA)", root partition contains the extracted core-image-sato-beaglebone.tar.bz2 "/dev/sde2       147456 62521343 62373888 29.8G 83 Linux"
Mar 12 16:12:31 <jose__> the serial console only shows "CCCC" nothing comes up, any ideas what could be the issue?
Mar 12 16:20:36 <jose__> If I remove the boot flag from the boot partition, I see U-Boot loading "U-Boot 2018.01-00002-ge9ff418fb8 (Feb 20 2018 - 20:14:57 -0600), Build: jenkins-github_Bootloader-Builder-38"
Mar 12 16:27:57 <jose__> I can see the contents of the SD card from uBoot with "ext4ls mmc 0:2  ", then if I type boot seems that the image is try to boot from  TFTP and fails, TFTP from server 192.168.1.1; our IP address is 192.168.1.43
Mar 12 16:35:15 <yocti> New news from stackoverflow: BitBake recipe for custom setup.py <https://stackoverflow.com/questions/49239906/bitbake-recipe-for-custom-setup-py>
Mar 12 16:54:36 <majuk> jose__: #beagle would probably be more assistance.
Mar 12 16:58:08 <jose__> thanks majuk I will try there
Mar 12 17:35:28 <yocti> New news from stackoverflow: Booting Linux on i.MX6 SABRE Lite: Bad Data CRC ERROR: can't get kernel image <https://stackoverflow.com/questions/49177323/booting-linux-on-i-mx6-sabre-lite-bad-data-crc-error-cant-get-kernel-image>
Mar 12 18:21:41 <jww> good evening. does somebody use swupdate with yocto ? all the image I build have an error with u-boot telling  'Error: environment not initialized, No such file or directory', can somebody help please ? I'm new to yocto !
Mar 12 19:59:38 <lukma> jww: Please be sure that you have recent version of swupdate, u-boot and u-boot-fw-utils
Mar 12 20:01:18 <lukma> And the 'Error: environment not initialized' is on the side of u-boot
Mar 12 20:01:58 <lukma> it may happen that you want to access u-boot envs (via u-boot-fw-utils in userspace) as they are not initialized
Mar 12 20:02:11 <lukma> also you need /etc/fw_utils.conf
Mar 12 20:02:35 <lukma> in which you state where u-boot-fw-utils (fw_printenv) shall look for stored envs
Mar 12 22:40:51 <jose__> So I create yocto build from rocko, for bb .wic image seems bogus, it doesn't boot, I can get it to work if I install the MLO and u-boot.img in the SDCARD MBR...
Mar 12 22:41:04 <jose__> stil the image expect root fs on partition 2
Mar 12 22:44:49 <jose__> I ask on #beagle and I was told the problem is that MLO build by yocto is prepended by a raw mmc boot header and that am335x doesn't accept those on a FAT partition
Mar 13 01:06:56 <yocti> New news from stackoverflow: libva version error on yocto build <https://stackoverflow.com/questions/49246751/libva-version-error-on-yocto-build>
**** ENDING LOGGING AT Tue Mar 13 03:00:03 2018