Re: [yocto] Separate out image generation into a new task

2016-01-16 Thread Markus Volk
I found the mistake. The Problem seems to be the hyphen in the IMAGE_CMD name

IMAGE_CMD_hd1-usbimgdidn´t work
IMAGE_CMD_usbimgdoes

I´m curious if it still works with IMAGE_CMD_rpi-sdimg on the raspberrypi. Has 
someone already tried ?

> 
> Thank you,
> 
> unfortunately this has´t solved the problem for me
> 
>> Am 15.01.2016 um 02:56 schrieb Andre McCurdy :
>> 
>> On Wed, Jan 13, 2016 at 12:36 PM, Markus Volk  wrote:
>>> With the recent improvements in the master branch regarding image creation 
>>> i´m not able to build usb images anymore.
>> 
>> This patch might help:
>> 
>> http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115474.html
>> 
>>> do_image_ext3 and do_image_jffs2 works well, then i´m getting this error 
>>> message:
>>> 
>>> Log data follows:
>>> | DEBUG: Executing python function set_image_size
>>> | DEBUG: Python function set_image_size finished
>>> | DEBUG: Executing shell function do_image_hd1-usbimg
>>> | 
>>> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/run.do_image_hd1-usbimg.126432:
>>>  108: 
>>> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/run.do_image_hd1-usbimg.126432:
>>>  do_image_hd1-usbimg: not found
>>> | WARNING: exit code 127 from a shell command.
>>> | ERROR: Function failed: do_image_hd1-usbimg (log file is located at 
>>> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/log.do_image_hd1-usbimg.126432)
>>> ERROR: Task 18 
>>> (/home/flk/yocto/poky/meta-neutrino/recipes-images/images/neutrino-image.bb,
>>>  do_image_hd1-usbimg) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 2349 tasks of which 742 didn't need to be 
>>> rerun and 1 failed.
>>> Waiting for 0 running tasks to finish:
>>> 
>>> Summary: 1 task failed:
>>> /home/flk/yocto/poky/meta-neutrino/recipes-images/images/neutrino-image.bb, 
>>> do_image_hd1-usbimg
>>> Summary: There were 3 WARNING messages shown.
>>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>> 
>>> 
>>> Until now i used this file for building an usb image (very similar to the 
>>> way the sd image for raspberrypi is created):
>>> 
>>> usb_image-hd1.bbclass:
>>> 
>>> inherit image_types
>>> 
>>> #
>>> ## this is heavily inspired by the raspberry pi sdimage class.
>>> #
>>> # Create an image that can by written onto an USB stick.
>>> #
>>> # The disk layout used is:
>>> #
>>> #0  -> IMAGE_ROOTFS_ALIGNMENT - reserved for other 
>>> data
>>> #IMAGE_ROOTFS_ALIGNMENT -> BOOT_SPACE - u-boot script and 
>>> kernel
>>> #BOOT_SPACE -> USBIMG_SIZE - rootfs
>>> #
>>> # Default Free space = 
>>> 1.3x
>>> # Use 
>>> IMAGE_OVERHEAD_FACTOR to add more space
>>> # <->
>>> #1MiB  20MiB   USBIMG_ROOTFS
>>> # <---> <--> <-->
>>> #    
>>> # | IMAGE_ROOTFS_ALIGNMENT | BOOT_SPACE | ROOTFS_SIZE|
>>> #    
>>> # ^^^^
>>> # ||||
>>> # 0  1MiB 1MiB + 20MiB   1MiB + 20Mib + 
>>> USBIMG_ROOTFS
>>> 
>>> # This image depends on the rootfs image
>>> IMAGE_TYPEDEP_hd1-usbimg = "${USBIMG_ROOTFS_TYPE}"
>>> 
>>> # Boot partition volume id
>>> BOOTDD_VOLUME_ID ?= "KERNEL"
>>> 
>>> # Boot partition size [in KiB] (will be rounded up to 
>>> IMAGE_ROOTFS_ALIGNMENT)
>>> BOOT_SPACE ?= "20480"
>>> 
>>> # Set alignment to 4MB [in KiB]
>>> IMAGE_ROOTFS_ALIGNMENT = "1024"
>>> 
>>> # Use an uncompressed ext3 by default as rootfs
>>> USBIMG_ROOTFS_TYPE ?= "ext3"
>>> USBIMG_ROOTFS = "${IMAGE_NAME}.rootfs.${USBIMG_ROOTFS_TYPE}"
>>> 
>>> IMAGE_DEPENDS_hd1-usbimg = " \
>>>   parted-native \
>>>   mtools-native \
>>>   dosfstools-native \
>>>   virtual/kernel \
>>> "
>>> 
>>> # USB image name
>>> USBIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.hd1-usbimg"
>>> 
>>> # Compression method to apply to USBIMG after it has been created. Supported
>>> # compression formats are "gzip", "bzip2" or "xz". The original .hd1-usbimg 
>>> file
>>> # is kept and a new compressed file is created if one of these compression
>>> # formats is chosen. If USBIMG_COMPRESSION is set to any other value it is
>>> # silently ignored.
>>> #USBIMG_COMPRESSION ?= ""
>>> 
>>> # Additional files and/or directories to be copied into the vfat partition 
>>> from the IMAGE_ROOTFS.
>>> FATPAYLOAD ?= ""
>>> 
>>> IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
>>> 

[yocto] Is python distutils set to used the cross compiler by default somehow?

2016-01-16 Thread Jeff Waller
I’m attempting to do the following

pip install dronekit 

which is failing with 

unable to execute arm-oe-linux-gnueabi-gcc: No such file or directory

I just want it to use gcc, and in fact this helps

CC=gcc pip install dronekit

but it fails later on during the link step which is helped by setting LDSHARED, 
but
that again doesn’t help completely because the linker options are different for 
gcc executing on the drone (needs -lpthread perhaps…)

But I’m trying to understate where arm-oe-linux-gnueabi-gcc  is coming form in 
the first
place.  Is there some config file to set to have it not do this?

This is my first stop, it seems strange that such a specific (Open Embedded) 
compiler would
be used by default on a target system.

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