[yocto] enable fortran in yocto

2016-02-10 Thread Liubchynskyi, Stanislav (Nokia - PL/Wroclaw) 

Hi,
I want to add fortran support to yocto build. I try different way whitch 
describe in the ethernet but enyone does't work. I use fido branch and gcc 4.9. 
Can you describe me step by step how to enable fortran in yocto or where I can 
find work instruction.
Thanks for help.


Best regards,

Stanislav Liubchynskyi
Software Developer, LFS, OPSW Wroclaw
Mobile Broadband, Nokia Networks

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

[yocto] QA error while building bitbake package

2016-02-10 Thread Renjith Vijayan 
Hi All,

I am new to Yocto bitbake concept & while building my package running in to
following QA build error.

ERROR: QA Issue: test-repo: Files/directories were installed but not
shipped in any package:
  /etc
  /etc/test
  /etc/test/yamls
  /etc/test/yamls/abc1.yaml
  /etc/test/yamls/abc2.yaml
  /etc/test/yamls/abc3.yaml
Please set FILES such that these items are packaged. Alternatively if they
are unneeded, avoid installing them or delete them within do_install.
[installed-vs-shipped]

The following is my bb file content for installing these paths:

do_compile() {
 cd ${S}
 distutils_do_compile
 # Cmake compile changes to the B directory
 cmake_do_compile
}

do_install() {
 cd ${S}
 distutils_do_install
 # Cmake compile changes to the B directory
 cmake_do_install
}

do_install_append(){
   install -d   ${D}/etc/test/yamls
   install -c -m 755 ${S}/conf/*.yaml ${D}/etc/test/yamls
}

FILES_${PN} += "/usr/lib/cli/plugins/ \
/etc \
/etc/test \
/etc/test/yamls \
/etc/test/yamls/abc1.yaml \
/etc/test/yamls/abc2.yamll \
/etc/test/yamls/abc3.yaml"

inherit  setuptools cmake


Could anyone point to me what i am doing wrong here?

Thanks in Advance,
Renjith
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH V2] linux-raspberry.inc: add initramfs support

2016-02-10 Thread Stéphane Cerveau 
append initramfs creation to install RPi bootloader trailer

Signed-off-by: Stéphane Cerveau 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 9 +
 1 file changed, 9 insertions(+)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 70e8bfe..74dbf19 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -64,4 +64,13 @@ do_rpiboot_mkimage() {
 fi
 fi
 }
+do_bundle_initramfs_append() {
+if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
+if test -n "${KERNEL_DEVICETREE}"; then
+# Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
+${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+fi
+fi
+}
+
 addtask rpiboot_mkimage before do_install after do_compile
-- 
2.1.4

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

[yocto] DTB without USB host

2016-02-10 Thread Marius Liebenberg 
Hi does anyone know if there is a standard DTB for BBB that does not 
have USB host, network interface and HDMI?




-
Regards / Groete

Marius D. Liebenberg
+27 82 698 3251
+27 12 743 6064
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] request BKM on distributed build

2016-02-10 Thread Ding, Yunliang 
Hi,

Does anyone who has a BKM on distributed build on Yocto?
>From the docs, IceCream was supported, anyone who can share some information 
>on how to enable it would be much appreciated!
Thanks a lot in advance!

BRs,
Ding Yunliang

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

[yocto] [meta-raspberrypi][PATCH] linux-raspberry.inc: add initramfs support

2016-02-10 Thread Stéphane Cerveau 
in do_rpiboot_mkimage add rpi bootload trailer
for initramfs image.

Signed-off-by: Stéphane Cerveau 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 70e8bfe..634bd5e 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -61,6 +61,9 @@ do_rpiboot_mkimage() {
 if test -n "${KERNEL_DEVICETREE}"; then
 # Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
 ${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok 
${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
+if [ ! -z "${INITRAMFS_IMAGE}" ]; then
+
${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+fi
 fi
 fi
 }
-- 
2.1.4

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

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

2016-02-10 Thread Woronicz, Bartosz ( NSN - PL/Wroclaw) 


On 09.02.2016 14:56, EXT Burton, Ross wrote:


On 9 February 2016 at 13:51, Woronicz, Bartosz ( NSN - PL/Wroclaw) 
> wrote:


Here is the whole bbclass/:
/

DESCRIPTION = "Creates symlink to the latest version workdir
of the package"

do_latest_link() {
if [ -n "${WORKDIR}" ]; then
linkname="$(dirname ${WORKDIR})/latest"
rm -f $linkname
ln -s $(basename ${WORKDIR}) $linkname
fi
}
addtask latest_link after do_unpack

do_unpack[postfuncs] += "do_latest_link"


But for better understanding I made the more throughout look into
the documentations. I found the information about "postfuncs" you
talk about [1]. However, the tasks description [2] doesn't say
anything about including the task in the process, it just
describes the demanded order that the task is put ( addtask
something after|before othertask ).

That is so, until I read "3.6. Variable Flags"  [3]. Where is
quite clearly stated those variables control functionality and
*dependencies*.
The documentation is quite unclear in that case.


If you're using a postfunc you don't need to addtask at all: using 
postfuncs means you don't need to have a separate task at all.


Ross
Ok, I understand now that 'addtask' is only necessary when I need 
seperate task to run. I think you solved my issue. Thanks again!


Kind regards,
Bartosz Woronicz
Engineer, Software Configuration (SCM)
NSN - PL/Wroclaw

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

[yocto] [meta-intel]: Grub file not created after building the image with bitbake -k linux-yocto

2016-02-10 Thread Shubham Kumar 
Hi all,

I'm new to Yocto build environment . I have been following the
documentations to start building my own image with various
customizations. So, my below question may seem very basic to you, for
which I apologize in advance :).

I am working on Intel Galileo Gen2
I cloned the Jethro layer in my local repository, and I also cloned
"meta-intel" layer. First I gave a try on core-image-minimal using wic
tool. The generated image contained the required grub file and The
hardware was successfully able to boot with this image.

After all this, I tried to generate the full Linux image using
"bitbake -k linux-yocto". I added a custom layer just for the purpose
of learning, and also included a few packages to be built like
strace,,tools-sdk,tools-debug,etc. I followed the Yocto documentation
for all this.

It took very less time since the no. of tasks that needed to be run
were comparatively very less as those during core-image-minimal.I did
all this in a different build directory from the one I used for
core-image-minimal. The images were then created in
tmp/deploy/images/intel-quark.

But this folder didn't contain any Grub file. Why was this grub file
not created during this image creation? Did I miss anything in the
steps followed??
Waiting for your responses .

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

[yocto] dtb filename mismatch prevents booting

2016-02-10 Thread Oliver Graute 
Hello list,

if I try to boot from my yocto generated SD-card image my u-boot can't
start the kernel because the imx6ul-14x14-evk.dtb is missing.


reading boot.scr
** Unable to read file boot.scr **
reading zImage
5072288 bytes read in 328 ms (14.7 MiB/s)
Booting from mmc ...
reading imx6ul-14x14-evk.dtb
** Unable to read file imx6ul-14x14-evk.dtb **
Kernel image @ 0x8200 [ 0x00 - 0x4d65a0 ]

Starting kernel ...


In my /boot folder I saw a dtb file, but the filename is a bit different.

zImage-imx6ul-14x14-evk.dtb instead of imx6ul-14x14-evk.dtb

So I changed these filename manually and my Image is booting.

mv zImage-imx6ul-14x14-evk.dtb imx6ul-14x14-evk.dtb
»zImage-imx6ul-14x14-evk.dtb“ -> »imx6ul-14x14-evk.dtb“

What is the right way to define these dtb filename?

I saw the IMAGE_BOOT_FILES in local.conf

#IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb"
IMAGE_BOOT_FILES = "zImage imx6ul-14x14-evk.dtb"

but after I changed it my build fails.

ERROR: Error: The image creation script 
'/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic'
 returned 1:
Error: exec_cmd: install -m 0644 -D 
/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/deploy/images/imx6ulevk/imx6ul-14x14-evk.dtb
 
/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/deploy/images/imx6ulevk/fsl-image-imx6ulevk-20160208144228/build/boot/imx6ul-14x14-evk.dtb
 returned '1' instead of 0
Checking basic build environment...
Done.

Creating image(s)...

WARNING: 
/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic:1
 exit 1 from
  BUILDDIR=/home/graute/5411_IBIS/yocto/build-imx6ulevk wic create $wks --vars 
/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/sysroots/imx6ulevk/imgdata/ -e 
fsl-image -o $out/

ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/log.do_rootfs.17681
ERROR: Task 7 
(/home/graute/5411_IBIS/yocto/os-meta-dnt/meta-fsl/recipes-fsl/images/fsl-image.bb,
 do_rootfs) failed with exit code '1'

some ideas whats going wrong here?

Best regards,

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

Re: [yocto] Debugging shared libraries

2016-02-10 Thread Mark Hatle 
On 2/10/16 1:31 AM, Gary Thomas wrote:
> I'm trying to debug some code (mplayer) which uses some shared
> libraries from ffmpeg.  When I use GDB (via gdbserver), I don't
> get all the debug information I need - note that many of the shared
> libraries do not have any symbolic debugging info:

Is your system using the the split debug binaries, and if so, do you have them
all installed on the system that GDB is running on?

(When GDB starts, you should see it load the symbols, or error it can't find 
them.)

Assuming you DO have the symbol files available, and some things are lacking
debuginfo, it's possible those recipes are not properly building with full
symbols (they should be, the whole system should be.)

Easiest way to check is do a readelf/objdump on the .debug version of the
library and check that there are dwarf symbols present... if not, it's probably
a recipe error.

--Mark

> (gdb) info sharedlibrary
>  FromTo  Syms Read   Shared Object Library
> 0xb6fcf800  0xb6feaf08  Yes /tmp/p0382.img/lib/ld-linux-armhf.so.3
> 0xb6fa6fa8  0xb6fb2b40  Yes (*) /tmp/p0382.img/lib/libtinfo.so.5
> 0xb6f6d210  0xb6f8c200  Yes /tmp/p0382.img/usr/lib/libpng16.so.16
> 0xb6f488e8  0xb6f54a60  Yes /tmp/p0382.img/lib/libz.so.1
> 0xb6f069f0  0xb6f34264  Yes /tmp/p0382.img/usr/lib/libjpeg.so.8
> 0xb6edbaf0  0xb6eee29c  Yes /tmp/p0382.img/usr/lib/libdvdread.so.4
> 0xb6eb6108  0xb6ec7ae8  Yes /tmp/p0382.img/usr/lib/libass.so.4
> 0xb6e808b8  0xb6e95384  Yes /tmp/p0382.img/usr/lib/libvorbis.so.0
> 0xb6e6b4b4  0xb6e6d7e4  Yes /tmp/p0382.img/usr/lib/libogg.so.0
> 0xb6e48978  0xb6e55eb4  Yes /tmp/p0382.img/usr/lib/libspeex.so.1
> 0xb6dfe818  0xb6e1b8b4  Yes (*) /tmp/p0382.img/usr/lib/libfaad.so.2
> 0xb6d92df0  0xb6dd4e78  Yes (*) /tmp/p0382.img/usr/lib/libavutil.so.54
> 0xb5de0640  0xb64a2e18  Yes (*) /tmp/p0382.img/usr/lib/libavcodec.so.56
> 0xb5c17528  0xb5d65840  Yes (*) /tmp/p0382.img/usr/lib/libavformat.so.56
> 0xb5b81688  0xb5be8db8  Yes (*) /tmp/p0382.img/usr/lib/libswscale.so.3
> 0xb5b5f578  0xb5b6c718  Yes (*) /tmp/p0382.img/usr/lib/libswresample.so.1
> 0xb5b44998  0xb5b4b490  Yes (*) /tmp/p0382.img/usr/lib/libpostproc.so.53
> 0xb5b1f0e0  0xb5b2e194  Yes /tmp/p0382.img/lib/libpthread.so.0
> 0xb5aa4c00  0xb5ad46d0  Yes /tmp/p0382.img/lib/libm.so.6
> 0xb5a859ec  0xb5a8fc34  Yes /tmp/p0382.img/usr/lib/libXext.so.6
> 0xb597b728  0xb59f92bc  Yes /tmp/p0382.img/usr/lib/libX11.so.6
> 0xb5946fc8  0xb59573d0  Yes /tmp/p0382.img/usr/lib/libtheoradec.so.1
> 0xb5887910  0xb591bbb8  Yes (*) /tmp/p0382.img/usr/lib/libasound.so.2
> 0xb58579f8  0xb58586ac  Yes /tmp/p0382.img/usr/lib/libXss.so.1
> 0xb5844ca0  0xb5846bac  Yes /tmp/p0382.img/usr/lib/libXv.so.1
> 0xb57e7700  0xb58265e0  Yes /tmp/p0382.img/usr/lib/libSDL-1.2.so.0
> 0xb56bae00  0xb57abb28  Yes /tmp/p0382.img/lib/libc.so.6
> 0xb569292c  0xb5693724  Yes /tmp/p0382.img/lib/libdl.so.2
> 0xb5650a70  0xb566e6a4  Yes /tmp/p0382.img/usr/lib/libfontconfig.so.1
> 0xb561e324  0xb563951c  Yes /tmp/p0382.img/usr/lib/libexpat.so.1
> 0xb559d36c  0xb55f5cb4  Yes /tmp/p0382.img/usr/lib/libfreetype.so.6
> 0xb55622b0  0xb5567e84  Yes /tmp/p0382.img/usr/lib/libenca.so.0
> 0xb541fbc0  0xb54b5a08  Yes (*) /tmp/p0382.img/usr/lib/libx264.so.144
> 0xb53d4df0  0xb53fa0b0  Yes /tmp/p0382.img/usr/lib/libtheoraenc.so.1
> 0xb53a72b0  0xb53bd258  Yes (*) /tmp/p0382.img/usr/lib/liblzma.so.5
> 0xb5386050  0xb5392cc0  Yes (*) /tmp/p0382.img/usr/lib/libbz2.so.0
> 0xb5367810  0xb5373b30  Yes /tmp/p0382.img/usr/lib/libxcb.so.1
> 0xb534da00  0xb534e5a8  Yes /tmp/p0382.img/usr/lib/libXau.so.6
> 0xb5339f80  0xb533b69c  Yes /tmp/p0382.img/usr/lib/libXdmcp.so.6
> 0xb5323720  0xb5326ea0  Yes /tmp/p0382.img/lib/librt.so.1
> 0xb530b6e0  0xb5311234  Yes /tmp/p0382.img/usr/lib/libXrandr.so.2
> 0xb52f3530  0xb52f9060  Yes /tmp/p0382.img/usr/lib/libXrender.so.1
> 0xb52d3160  0xb52e18a4  Yes /tmp/p0382.img/lib/libgcc_s.so.1
> (*): Shared library is missing debugging information.
> 
> Is this a function of how those libraries were built (by the recipe)
> or something else?  How can I get the symbolic debugging info enabled?
> 
> Thanks for any pointers
> 

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

[yocto] wic: Setting partition id value?

2016-02-10 Thread Usman, Fahad 

Hi,
Is there a way to create a partition with an arbitrary partition id, 
using wic tool. We want to create a disk image using wic for Altera 
Cyclone V. It require the partition id to be set to a particular hex 
value for the partition it reads the boot loader binary from. The 
partition id does get set automatically to the correct value depending 
on the value of fstype (eg. 0x83 for ext3 or 0x0c for fat32), but I 
couldn't find a way to set it to an arbitrary value.


Best regards,
Fahad Usman.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto/Poky with external linaro toolchain

2016-02-10 Thread Christopher Larson 
https://github.com/MentorEmbedded/meta-mentor/blob/master/meta-mel/conf/include/drop-toolchain-from-sdk.inc
may
be of interest to you.

On Wed, Feb 10, 2016 at 9:01 AM Thomas Kaufmann 
wrote:

> Hi
>
>
>
> I started porting an existing linux system to the latest yocto base. The
> hardware TI am 335x based.
>
> I want to use the external linaro toolchains. Since I use an existing 3.2
> linux kernel as well as an older u-boot, I created a own machine and distro
> configuration. I succeed to build and run the target, so far so good.
>
>
>
> To incorporate the external toolchains I added
>
>
>
> TCMODE = "external-linaro"
>
> EXTERNAL_TOOLCHAIN =
> "//gcc-linaro-5.1-2015.08-x86_64_arm-linux-gnueabihf"
>
>
>
> to the local.conf file and
>
>
>
> meta-linaro/meta-linaro-toolchain
>
>
>
> to the BBLAYERS in bblayers.conf. meta-linaro was cloned using git.
>
> For my "legacy" packages I adjust "EXTERNAL_TOOLCHAIN" to a gcc-4.9
> version, this seems to work and everything compiles.
>
>
>
> Now my next step is to create an SDK distribution.
>
> When I do do_populate_sdk with bitbake for my image, however the process
> seems to compile a new cross compiler for the target as well as various
> qemu things and also newer kernel releases.
>
>
>
> Is this the preferred way to integrate the linaro toolchain into poky? Can
> anybody share their experience? I find various presentations and snippets
> about this topic, but nothing is complete.
>
> How do I create a SDK distribution which does not feature any QEMU (I want
> to deploy to target hardware) and uses the existing prebuilt toolchain?
> Build host and target sdk host would be x86_64.
>
>
>
> Any recommendations are welcome.
>
>
>
> regards Thomas Kaufmann
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto/Poky with external linaro toolchain

2016-02-10 Thread Thomas Kaufmann 
Hi

I started porting an existing linux system to the latest yocto base. The 
hardware TI am 335x based.
I want to use the external linaro toolchains. Since I use an existing 3.2 linux 
kernel as well as an older u-boot, I created a own machine and distro 
configuration. I succeed to build and run the target, so far so good.

To incorporate the external toolchains I added

TCMODE = "external-linaro"
EXTERNAL_TOOLCHAIN = 
"//gcc-linaro-5.1-2015.08-x86_64_arm-linux-gnueabihf"

to the local.conf file and

meta-linaro/meta-linaro-toolchain

to the BBLAYERS in bblayers.conf. meta-linaro was cloned using git.
For my "legacy" packages I adjust "EXTERNAL_TOOLCHAIN" to a gcc-4.9 version, 
this seems to work and everything compiles.

Now my next step is to create an SDK distribution.
When I do do_populate_sdk with bitbake for my image, however the process seems 
to compile a new cross compiler for the target as well as various qemu things 
and also newer kernel releases.

Is this the preferred way to integrate the linaro toolchain into poky? Can 
anybody share their experience? I find various presentations and snippets about 
this topic, but nothing is complete.
How do I create a SDK distribution which does not feature any QEMU (I want to 
deploy to target hardware) and uses the existing prebuilt toolchain? Build host 
and target sdk host would be x86_64.

Any recommendations are welcome.

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

[yocto] Eclipse IDE plugin failure

2016-02-10 Thread Marius 
I installed the latest Eclipse (Mars) and attempted to install the 
plugin. The installation failed and the reported error was that it could 
not locate the TM Terminal version 3.xxx. The TM terminal is installed 
but it is version 4.00xxx


Should I rather install older versions of the software or is there a 
workaround for this problem? If so what is suggested to be good and 
working?



-
Regards / Groete

Marius D. Liebenberg
+27 82 698 3251
+27 12 743 6064
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dtb filename mismatch prevents booting

2016-02-10 Thread Maciej Borzecki 

> Dnia 10 luty 2016 o 17:16 Oliver Graute  napisał(a):
>
>
> Hello list,
>
> if I try to boot from my yocto generated SD-card image my u-boot can't
> start the kernel because the imx6ul-14x14-evk.dtb is missing.
>
>
> reading boot.scr
> ** Unable to read file boot.scr **
> reading zImage
> 5072288 bytes read in 328 ms (14.7 MiB/s)
> Booting from mmc ...
> reading imx6ul-14x14-evk.dtb
> ** Unable to read file imx6ul-14x14-evk.dtb **
> Kernel image @ 0x8200 [ 0x00 - 0x4d65a0 ]
>
> Starting kernel ...
>
>
> In my /boot folder I saw a dtb file, but the filename is a bit different.
>
> zImage-imx6ul-14x14-evk.dtb instead of imx6ul-14x14-evk.dtb
>
> So I changed these filename manually and my Image is booting.
>
> mv zImage-imx6ul-14x14-evk.dtb imx6ul-14x14-evk.dtb
> »zImage-imx6ul-14x14-evk.dtb“ -> »imx6ul-14x14-evk.dtb“
>
> What is the right way to define these dtb filename?
>
> I saw the IMAGE_BOOT_FILES in local.conf
>
> #IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb"
> IMAGE_BOOT_FILES = "zImage imx6ul-14x14-evk.dtb"
>
> but after I changed it my build fails.
>
> ERROR: Error: The image creation script
> '/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic'
> returned 1:
> Error: exec_cmd: install -m 0644 -D
> /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/deploy/images/imx6ulevk/imx6ul-14x14-evk.dtb
> /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/deploy/images/imx6ulevk/fsl-image-imx6ulevk-20160208144228/build/boot/imx6ul-14x14-evk.dtb
> returned '1' instead of 0
> Checking basic build environment...
> Done.
>
> Creating image(s)...
>
> WARNING:
> /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic:1
> exit 1 from
> BUILDDIR=/home/graute/5411_IBIS/yocto/build-imx6ulevk wic create $wks --vars
> /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/sysroots/imx6ulevk/imgdata/
> -e fsl-image -o $out/
>
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/log.do_rootfs.17681
> ERROR: Task 7
> (/home/graute/5411_IBIS/yocto/os-meta-dnt/meta-fsl/recipes-fsl/images/fsl-image.bb,
> do_rootfs) failed with exit code '1'
>
> some ideas whats going wrong here?
>

IIRC the usual way was to add kernel-devicetree package and let u-boot
pick the proper dtb during boot.

As for IMAGE_BOOT_FILES, you can tell wic to automatically rename files
by passing the desired name after a semicolon like this:

  IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;mx6ul-14x14-evk.dtb"

--
Maciej Borzęcki
Senior Software Engineer at Open-RnD Sp. z o.o.
www.open-rnd.pl, Facebook, Twitter
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Inline Python function name define

2016-02-10 Thread Christopher Larson 
def foo(d):
# Do something

FOO = "${@foo(d)}"

On Wed, Feb 10, 2016 at 12:02 PM Xi Zhou Zhou 
wrote:

> Hi,
>
> I want to manipulate a variable with inline python function in a recipe.
> The code is something like this.
>
> python newpv() {
> return 999
> }
>
> PV = "${@newpv()}"
>
>
> The error is "name 'newpv' is not defined"
>
> ERROR: ExpansionError during parsing /home/joelz/poky/build/
> ../meta-test/recipes-bsp/mytest/mytest.bb: Failure expanding variable PV,
> expression was ${@newpv()} which triggered exception NameError: name
> 'newpv' is not defined
>
>
> What's the right way to create inline python function in Yocto recipe?
>
>
> Thanks,
> Joel
> --
> ___
> 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] wic adds wrong mount lines to my fstab

2016-02-10 Thread Oliver Graute 
On Wed, Feb 10, 2016 at 11:19 AM, Ed Bartosh  wrote:
> Hi Oliver,
>
> On Tue, Feb 09, 2016 at 09:29:16AM +0100, Oliver Graute wrote:
>> # It uses SPL and u-boot
>> #
>> # The disk layout used is:
>> #  - - - --  - -- 
>> # | | SPL | u-boot  |  /boot1  | /boot2 | rootfs1 | rootfs2  |data|
>> #  - - - --  - -- 
>> # ^ ^ ^ ^ ^  ^
>> # | | | | |  |
>> # 0 1kiB  69kiB 4MiB   4MiB + 20MiB4MiB + 8Mib + rootfs1 + rootfs2 + 
>> data
>> #
>> part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk 
>> --no-table --align 1
>> part u-boot --source rawcopy --sourceparams="file=u-boot.img" --ondisk 
>> mmcblk --no-table --align 69
>> part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label 
>> boot --active --align 4096 --size 20M --extra-space 0
>> #part /boot2 --source bootimg-partition --ondisk mmcblk --fstype=vfat 
>> --label boot2 --active --align 4096 --size 8M --extra-space 0
>> part / --source rootfs --ondisk mmcblk --fstype=ext3 --label root --align 4 
>> --size 125
>> part /rescue --source rootfs --ondisk mmcblk --fstype=ext3 --label secondary 
>> --align 4 --size 125
>> part /data --ondisk mmcblk --fstype=ext3 --label data --align 4 --size 730
>>
>> Some sugesstions to fix this?
> How exactly wic complains if you use --ondisk mmcblk0 ?
>
> It worked for me with this .wks:
> part /boot --source bootimg-pcbios --ondisk mmcblk0 --label boot --active 
> --align 1024
> part / --source rootfs --ondisk mmcblk0 --fstype=ext3 --label root --align 
> 1024
> part /rescue --source rootfs --ondisk mmcblk0 --fstype=ext3 --label secondary 
> --align 4 --size 125
> part /data --ondisk mmcblk0 --fstype=ext3 --label data --align 4 --size 730
>
> bootloader --timeout=0 --append="rootwait rootfstype=ext3 console=tty0"
>
> and produced these 2 lines in fstab:
> /dev/mmcblk0p3  /rescue ext3defaults0   0
> /dev/mmcblk0p5  /data   ext3defaults0   0
>
> If you provide more info about your setup(layers used?) I can try to
> reproduce it and fix the issue.
> Creating bug in https://bugzilla.yoctoproject.org would be great too.

Hello Ed,

it is working now with --ondisk mmcblk0. I'am not sure why it didn't
worked before. I can't reproduce it anymore. Thx for your help and sorry
for the noise.

best regards,

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

[yocto] Inline Python function name define

2016-02-10 Thread Xi Zhou Zhou 
Hi,

I want to manipulate a variable with inline python function in a recipe.
The code is something like this.

python newpv() {
return 999
}

PV = "${@newpv()}"


The error is "name 'newpv' is not defined"

ERROR: ExpansionError during parsing /home/joelz/poky/build/
../meta-test/recipes-bsp/mytest/mytest.bb: Failure expanding variable PV,
expression was ${@newpv()} which triggered exception NameError: name 'newpv'
is not defined


What's the right way to create inline python function in Yocto recipe?


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

Re: [yocto] Debugging shared libraries

2016-02-10 Thread Khem Raj 

> On Feb 10, 2016, at 8:35 AM, Mark Hatle  wrote:
> 
> On 2/10/16 1:31 AM, Gary Thomas wrote:
>> I'm trying to debug some code (mplayer) which uses some shared
>> libraries from ffmpeg.  When I use GDB (via gdbserver), I don't
>> get all the debug information I need - note that many of the shared
>> libraries do not have any symbolic debugging info:
> 
> Is your system using the the split debug binaries, and if so, do you have them
> all installed on the system that GDB is running on?
> 
> (When GDB starts, you should see it load the symbols, or error it can't find 
> them.)
> 
> Assuming you DO have the symbol files available, and some things are lacking
> debuginfo, it's possible those recipes are not properly building with full
> symbols (they should be, the whole system should be.)
> 
> Easiest way to check is do a readelf/objdump on the .debug version of the
> library and check that there are dwarf symbols present... if not, it's 
> probably
> a recipe error.
> 
> --Mark
> 
>> (gdb) info sharedlibrary
>> FromTo  Syms Read   Shared Object Library
>> 0xb6fcf800  0xb6feaf08  Yes /tmp/p0382.img/lib/ld-linux-armhf.so.3
>> 0xb6fa6fa8  0xb6fb2b40  Yes (*) /tmp/p0382.img/lib/libtinfo.so.5
>> 0xb6f6d210  0xb6f8c200  Yes /tmp/p0382.img/usr/lib/libpng16.so.16
>> 0xb6f488e8  0xb6f54a60  Yes /tmp/p0382.img/lib/libz.so.1
>> 0xb6f069f0  0xb6f34264  Yes /tmp/p0382.img/usr/lib/libjpeg.so.8
>> 0xb6edbaf0  0xb6eee29c  Yes /tmp/p0382.img/usr/lib/libdvdread.so.4
>> 0xb6eb6108  0xb6ec7ae8  Yes /tmp/p0382.img/usr/lib/libass.so.4
>> 0xb6e808b8  0xb6e95384  Yes /tmp/p0382.img/usr/lib/libvorbis.so.0
>> 0xb6e6b4b4  0xb6e6d7e4  Yes /tmp/p0382.img/usr/lib/libogg.so.0
>> 0xb6e48978  0xb6e55eb4  Yes /tmp/p0382.img/usr/lib/libspeex.so.1
>> 0xb6dfe818  0xb6e1b8b4  Yes (*) /tmp/p0382.img/usr/lib/libfaad.so.2
>> 0xb6d92df0  0xb6dd4e78  Yes (*) /tmp/p0382.img/usr/lib/libavutil.so.54
>> 0xb5de0640  0xb64a2e18  Yes (*) /tmp/p0382.img/usr/lib/libavcodec.so.56
>> 0xb5c17528  0xb5d65840  Yes (*) /tmp/p0382.img/usr/lib/libavformat.so.56
>> 0xb5b81688  0xb5be8db8  Yes (*) /tmp/p0382.img/usr/lib/libswscale.so.3
>> 0xb5b5f578  0xb5b6c718  Yes (*) /tmp/p0382.img/usr/lib/libswresample.so.1
>> 0xb5b44998  0xb5b4b490  Yes (*) /tmp/p0382.img/usr/lib/libpostproc.so.53
>> 0xb5b1f0e0  0xb5b2e194  Yes /tmp/p0382.img/lib/libpthread.so.0
>> 0xb5aa4c00  0xb5ad46d0  Yes /tmp/p0382.img/lib/libm.so.6
>> 0xb5a859ec  0xb5a8fc34  Yes /tmp/p0382.img/usr/lib/libXext.so.6
>> 0xb597b728  0xb59f92bc  Yes /tmp/p0382.img/usr/lib/libX11.so.6
>> 0xb5946fc8  0xb59573d0  Yes /tmp/p0382.img/usr/lib/libtheoradec.so.1
>> 0xb5887910  0xb591bbb8  Yes (*) /tmp/p0382.img/usr/lib/libasound.so.2
>> 0xb58579f8  0xb58586ac  Yes /tmp/p0382.img/usr/lib/libXss.so.1
>> 0xb5844ca0  0xb5846bac  Yes /tmp/p0382.img/usr/lib/libXv.so.1
>> 0xb57e7700  0xb58265e0  Yes /tmp/p0382.img/usr/lib/libSDL-1.2.so.0
>> 0xb56bae00  0xb57abb28  Yes /tmp/p0382.img/lib/libc.so.6
>> 0xb569292c  0xb5693724  Yes /tmp/p0382.img/lib/libdl.so.2
>> 0xb5650a70  0xb566e6a4  Yes /tmp/p0382.img/usr/lib/libfontconfig.so.1
>> 0xb561e324  0xb563951c  Yes /tmp/p0382.img/usr/lib/libexpat.so.1
>> 0xb559d36c  0xb55f5cb4  Yes /tmp/p0382.img/usr/lib/libfreetype.so.6
>> 0xb55622b0  0xb5567e84  Yes /tmp/p0382.img/usr/lib/libenca.so.0
>> 0xb541fbc0  0xb54b5a08  Yes (*) /tmp/p0382.img/usr/lib/libx264.so.144
>> 0xb53d4df0  0xb53fa0b0  Yes /tmp/p0382.img/usr/lib/libtheoraenc.so.1
>> 0xb53a72b0  0xb53bd258  Yes (*) /tmp/p0382.img/usr/lib/liblzma.so.5
>> 0xb5386050  0xb5392cc0  Yes (*) /tmp/p0382.img/usr/lib/libbz2.so.0
>> 0xb5367810  0xb5373b30  Yes /tmp/p0382.img/usr/lib/libxcb.so.1
>> 0xb534da00  0xb534e5a8  Yes /tmp/p0382.img/usr/lib/libXau.so.6
>> 0xb5339f80  0xb533b69c  Yes /tmp/p0382.img/usr/lib/libXdmcp.so.6
>> 0xb5323720  0xb5326ea0  Yes /tmp/p0382.img/lib/librt.so.1
>> 0xb530b6e0  0xb5311234  Yes /tmp/p0382.img/usr/lib/libXrandr.so.2
>> 0xb52f3530  0xb52f9060  Yes /tmp/p0382.img/usr/lib/libXrender.so.1
>> 0xb52d3160  0xb52e18a4  Yes /tmp/p0382.img/lib/libgcc_s.so.1
>> (*): Shared library is missing debugging information.
>> 
>> Is this a function of how those libraries were built (by the recipe)
>> or something else?  How can I get the symbolic debugging info enabled?
>> 
>> Thanks for any pointers


Usually it works well if you add

EXTRA_IMAGE_FEATURES_append = “ dbg-pkgs”

image size grows but you get good debug view on target.

another option, I usually use is setup feeds
and then

opkg install -dbg

which pulls in a section of debug info needed to debug a given package.


>> 
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
>

Re: [yocto] Inline Python function name define

2016-02-10 Thread Xi Zhou Zhou 
The code works for me.


Thanks,
Joel

On Wed, Feb 10, 2016 at 2:04 PM, Christopher Larson 
wrote:

> def foo(d):
> # Do something
>
> FOO = "${@foo(d)}"
>
> On Wed, Feb 10, 2016 at 12:02 PM Xi Zhou Zhou 
> wrote:
>
>> Hi,
>>
>> I want to manipulate a variable with inline python function in a recipe.
>> The code is something like this.
>>
>> python newpv() {
>> return 999
>> }
>>
>> PV = "${@newpv()}"
>>
>>
>> The error is "name 'newpv' is not defined"
>>
>> ERROR: ExpansionError during parsing /home/joelz/poky/build/
>> ../meta-test/recipes-bsp/mytest/mytest.bb: Failure expanding variable
>> PV, expression was ${@newpv()} which triggered exception NameError: name
>> 'newpv' is not defined
>>
>>
>> What's the right way to create inline python function in Yocto recipe?
>>
>>
>> Thanks,
>> Joel
>> --
>> ___
>> 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] Debugging shared libraries

2016-02-10 Thread Gary Thomas 

On 2016-02-10 21:08, Khem Raj wrote:



On Feb 10, 2016, at 8:35 AM, Mark Hatle  wrote:

On 2/10/16 1:31 AM, Gary Thomas wrote:

I'm trying to debug some code (mplayer) which uses some shared
libraries from ffmpeg.  When I use GDB (via gdbserver), I don't
get all the debug information I need - note that many of the shared
libraries do not have any symbolic debugging info:


Is your system using the the split debug binaries, and if so, do you have them
all installed on the system that GDB is running on?

(When GDB starts, you should see it load the symbols, or error it can't find 
them.)

Assuming you DO have the symbol files available, and some things are lacking
debuginfo, it's possible those recipes are not properly building with full
symbols (they should be, the whole system should be.)

Easiest way to check is do a readelf/objdump on the .debug version of the
library and check that there are dwarf symbols present... if not, it's probably
a recipe error.

--Mark


(gdb) info sharedlibrary
 FromTo  Syms Read   Shared Object Library
0xb6fcf800  0xb6feaf08  Yes /tmp/p0382.img/lib/ld-linux-armhf.so.3
0xb6fa6fa8  0xb6fb2b40  Yes (*) /tmp/p0382.img/lib/libtinfo.so.5
0xb6f6d210  0xb6f8c200  Yes /tmp/p0382.img/usr/lib/libpng16.so.16
0xb6f488e8  0xb6f54a60  Yes /tmp/p0382.img/lib/libz.so.1
0xb6f069f0  0xb6f34264  Yes /tmp/p0382.img/usr/lib/libjpeg.so.8
0xb6edbaf0  0xb6eee29c  Yes /tmp/p0382.img/usr/lib/libdvdread.so.4
0xb6eb6108  0xb6ec7ae8  Yes /tmp/p0382.img/usr/lib/libass.so.4
0xb6e808b8  0xb6e95384  Yes /tmp/p0382.img/usr/lib/libvorbis.so.0
0xb6e6b4b4  0xb6e6d7e4  Yes /tmp/p0382.img/usr/lib/libogg.so.0
0xb6e48978  0xb6e55eb4  Yes /tmp/p0382.img/usr/lib/libspeex.so.1
0xb6dfe818  0xb6e1b8b4  Yes (*) /tmp/p0382.img/usr/lib/libfaad.so.2
0xb6d92df0  0xb6dd4e78  Yes (*) /tmp/p0382.img/usr/lib/libavutil.so.54
0xb5de0640  0xb64a2e18  Yes (*) /tmp/p0382.img/usr/lib/libavcodec.so.56
0xb5c17528  0xb5d65840  Yes (*) /tmp/p0382.img/usr/lib/libavformat.so.56
0xb5b81688  0xb5be8db8  Yes (*) /tmp/p0382.img/usr/lib/libswscale.so.3
0xb5b5f578  0xb5b6c718  Yes (*) /tmp/p0382.img/usr/lib/libswresample.so.1
0xb5b44998  0xb5b4b490  Yes (*) /tmp/p0382.img/usr/lib/libpostproc.so.53
0xb5b1f0e0  0xb5b2e194  Yes /tmp/p0382.img/lib/libpthread.so.0
0xb5aa4c00  0xb5ad46d0  Yes /tmp/p0382.img/lib/libm.so.6
0xb5a859ec  0xb5a8fc34  Yes /tmp/p0382.img/usr/lib/libXext.so.6
0xb597b728  0xb59f92bc  Yes /tmp/p0382.img/usr/lib/libX11.so.6
0xb5946fc8  0xb59573d0  Yes /tmp/p0382.img/usr/lib/libtheoradec.so.1
0xb5887910  0xb591bbb8  Yes (*) /tmp/p0382.img/usr/lib/libasound.so.2
0xb58579f8  0xb58586ac  Yes /tmp/p0382.img/usr/lib/libXss.so.1
0xb5844ca0  0xb5846bac  Yes /tmp/p0382.img/usr/lib/libXv.so.1
0xb57e7700  0xb58265e0  Yes /tmp/p0382.img/usr/lib/libSDL-1.2.so.0
0xb56bae00  0xb57abb28  Yes /tmp/p0382.img/lib/libc.so.6
0xb569292c  0xb5693724  Yes /tmp/p0382.img/lib/libdl.so.2
0xb5650a70  0xb566e6a4  Yes /tmp/p0382.img/usr/lib/libfontconfig.so.1
0xb561e324  0xb563951c  Yes /tmp/p0382.img/usr/lib/libexpat.so.1
0xb559d36c  0xb55f5cb4  Yes /tmp/p0382.img/usr/lib/libfreetype.so.6
0xb55622b0  0xb5567e84  Yes /tmp/p0382.img/usr/lib/libenca.so.0
0xb541fbc0  0xb54b5a08  Yes (*) /tmp/p0382.img/usr/lib/libx264.so.144
0xb53d4df0  0xb53fa0b0  Yes /tmp/p0382.img/usr/lib/libtheoraenc.so.1
0xb53a72b0  0xb53bd258  Yes (*) /tmp/p0382.img/usr/lib/liblzma.so.5
0xb5386050  0xb5392cc0  Yes (*) /tmp/p0382.img/usr/lib/libbz2.so.0
0xb5367810  0xb5373b30  Yes /tmp/p0382.img/usr/lib/libxcb.so.1
0xb534da00  0xb534e5a8  Yes /tmp/p0382.img/usr/lib/libXau.so.6
0xb5339f80  0xb533b69c  Yes /tmp/p0382.img/usr/lib/libXdmcp.so.6
0xb5323720  0xb5326ea0  Yes /tmp/p0382.img/lib/librt.so.1
0xb530b6e0  0xb5311234  Yes /tmp/p0382.img/usr/lib/libXrandr.so.2
0xb52f3530  0xb52f9060  Yes /tmp/p0382.img/usr/lib/libXrender.so.1
0xb52d3160  0xb52e18a4  Yes /tmp/p0382.img/lib/libgcc_s.so.1
(*): Shared library is missing debugging information.

Is this a function of how those libraries were built (by the recipe)
or something else?  How can I get the symbolic debugging info enabled?

Thanks for any pointers



Usually it works well if you add

EXTRA_IMAGE_FEATURES_append = “ dbg-pkgs”

image size grows but you get good debug view on target.

another option, I usually use is setup feeds
and then

opkg install -dbg

which pulls in a section of debug info needed to debug a given package.



I've done all this already.  The problem is that for the libraries which
have no symbols there are no corresponding -dbg packages :-(  I looked
at the ffmpeg recipe (where the libswresample library I'm most interested
in comes from) and there is serious magic involved in the

Re: [yocto] dtb filename mismatch prevents booting

2016-02-10 Thread Oliver Graute 
On 10/02/16, Maciej Borzecki wrote:
> 
> > Dnia 10 luty 2016 o 17:16 Oliver Graute  
> > napisał(a):
> >
> >
> > Hello list,
> >
> > if I try to boot from my yocto generated SD-card image my u-boot can't
> > start the kernel because the imx6ul-14x14-evk.dtb is missing.
> >
> >
> > reading boot.scr
> > ** Unable to read file boot.scr **
> > reading zImage
> > 5072288 bytes read in 328 ms (14.7 MiB/s)
> > Booting from mmc ...
> > reading imx6ul-14x14-evk.dtb
> > ** Unable to read file imx6ul-14x14-evk.dtb **
> > Kernel image @ 0x8200 [ 0x00 - 0x4d65a0 ]
> >
> > Starting kernel ...
> >
> >
> > In my /boot folder I saw a dtb file, but the filename is a bit different.
> >
> > zImage-imx6ul-14x14-evk.dtb instead of imx6ul-14x14-evk.dtb
> >
> > So I changed these filename manually and my Image is booting.
> >
> > mv zImage-imx6ul-14x14-evk.dtb imx6ul-14x14-evk.dtb
> > »zImage-imx6ul-14x14-evk.dtb“ -> »imx6ul-14x14-evk.dtb“
> >
> > What is the right way to define these dtb filename?
> >
> > some ideas whats going wrong here?
> >
> 
> IIRC the usual way was to add kernel-devicetree package and let u-boot
> pick the proper dtb during boot.
> 
> As for IMAGE_BOOT_FILES, you can tell wic to automatically rename files
> by passing the desired name after a semicolon like this:
> 
>   IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;mx6ul-14x14-evk.dtb"

ok that worked for me, I changed it like this

-IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb"
+IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;imx6ul-14x14-evk.dtb"

now the Image is directly booting without manually renaming.

thx for your help

Best Rgeards,

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

Re: [yocto] wic: Setting partition id value?

2016-02-10 Thread Usman, Fahad 

On 02/11/2016 07:03 AM, Jon Szymaniak wrote:
I ran into this problem as well, but with parted. My hack was to use 
dd to write the correct type ID into the image's MBR after I finished 
creating the partitions on the image file.

Thanks Jon Szymaniak,
I was also thinking about a similar solution, the reason wic has this 
limitation is probably because it uses parted under the hood and parted 
doesn't allow you to set the partition id to an arbitrary value. A safer 
way to do this might be with the help of fdisk as it allows you to 
change partition's system id using the 't' sub command in interactive 
mode. But I am looking for a way to do this using existing options in wic.


Regards,
Fahad Usman.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ClouchDB on Yocto

2016-02-10 Thread Stefano Cordibella 

Hi list,
I am working with CouchDB and I want to integrate it in Yocto.

The main issue is that it requires an old version of spidermonkey 
(1.8.5) and this version generate an illegal instruction on my runtime 
(an ARM borad based on Freescale imx6). I am trying to patch 
spidermonkey using a patch that I have found googling around... I have 
also writtten to the couchdb developer but I haven't received an answer 
for now.


So for now the question is: why CouchDB isn't yet in Yocto? Because it 
is to difficult to integrate (spidermonkey and other deps) or because it 
isn't so interesting?


Thank you for your time,
Stefano.

--
*Stefano Cordibella*
EDALab s.r.l. - Networked Embedded Systems

Strada Le Grazie, 15 - 37134 Verona - Italy
email : stefano.cordibe...@edalab.it
skype : stefano.cordibella
tel. : +39 045 802 70 85
web : www.edalab.it
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Disabling ipv6

2016-02-10 Thread Chris Trobridge 
I hit this issue experimenting with disabling ipv6, as Todd did originally, 
with an odd error about not being able to build the native sdk.
It's not a problem for me but is there a recommended way for disabling a libc 
distro feature like ipv6 without creating a whole new distro?  Does libc really 
require ipv6?  I can see it's the features in DISTRO_FEATURES_LIBC that are 
critical.
For the purposes of this experiment I added to local.conf to get it 
working:DISTRO_FEATURES_remove = "ipv6"DISTRO_FEATURES_LIBC_remove = "ipv6"
But I expect I will create a new distro at some point.
Cheers,Chris
On Tuesday 27 October 2015 08:45:26 Burton, Ross wrote:> On 26 October 2015 at 
20:16, Todd Efflam  wrote:> > Thanks for the tip.  We 
tried adding this to the local.conf file but> > it failed with the following 
error:> > ERROR: Nothing PROVIDES 'glibc'> > ERROR: glibc was skipped: missing 
required distro feature 'ipv6' (not> > in DISTRO_FEATURES)> > Ouch.  That's 
surely not right.> > The commit that introduced this was:> > commit 
97899bc908a421295d814801ff86edeb9304d2fd> Author: Chen Qi > Date:   Thu Jul 3 11:23:42 2014 +0800> > eglibc: check for 
required distro features> > If users accidently override the 
DISTRO_FEATURES in local.conf,> then build failures occur for lack of libc 
functions.> > All features in DISTRO_FEATURES_LIBC should be in 
DISTRO_FEATURES.> That's why this patch let the recipe inherit 
distro_features_check> class and set REQUIRED_DISTRO_FEATURES to 
"${DISTRO_FEATURES_LIBC}".> > [YOCTO #6381]> > But the entire point of the 
logic in glibc-options is to make these> options, well, optional.> > It looks 
like the required_distro_features use in eglibc is misguided.  Can> you comment 
out the REQUIRED_DISTRO_FEATURES assignment in glibc.inc and> verify that it 
then builds fine without ipv6 enabled?
Ah yes, I meant to get back to this at some point as I didn't really like how 
this was fixed previously either (see 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6381 for details of the 
problem). It seems to me that we should:
1) Fix the glibc recipes so that they handle an empty libc configuration or 
error out much earlier with a sensible message if that's not possible
2) Properly detect when DISTRO_FEATURES has been "zapped" via += in local.conf 
or elsewhere and show an error/warning about that.
Cheers,Paul
-- 
Paul EggletonIntel Open Source Technology Centre
  -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wic adds wrong mount lines to my fstab

2016-02-10 Thread Ed Bartosh 
Hi Oliver,

On Tue, Feb 09, 2016 at 09:29:16AM +0100, Oliver Graute wrote:
> # It uses SPL and u-boot
> #
> # The disk layout used is:
> #  - - - --  - -- 
> # | | SPL | u-boot  |  /boot1  | /boot2 | rootfs1 | rootfs2  |data|
> #  - - - --  - -- 
> # ^ ^ ^ ^ ^  ^
> # | | | | |  |
> # 0 1kiB  69kiB 4MiB   4MiB + 20MiB4MiB + 8Mib + rootfs1 + rootfs2 + 
> data
> #
> part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk 
> --no-table --align 1
> part u-boot --source rawcopy --sourceparams="file=u-boot.img" --ondisk mmcblk 
> --no-table --align 69
> part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label 
> boot --active --align 4096 --size 20M --extra-space 0
> #part /boot2 --source bootimg-partition --ondisk mmcblk --fstype=vfat --label 
> boot2 --active --align 4096 --size 8M --extra-space 0
> part / --source rootfs --ondisk mmcblk --fstype=ext3 --label root --align 4 
> --size 125
> part /rescue --source rootfs --ondisk mmcblk --fstype=ext3 --label secondary 
> --align 4 --size 125
> part /data --ondisk mmcblk --fstype=ext3 --label data --align 4 --size 730
>
> Some sugesstions to fix this?
How exactly wic complains if you use --ondisk mmcblk0 ?

It worked for me with this .wks:
part /boot --source bootimg-pcbios --ondisk mmcblk0 --label boot --active 
--align 1024
part / --source rootfs --ondisk mmcblk0 --fstype=ext3 --label root --align 1024
part /rescue --source rootfs --ondisk mmcblk0 --fstype=ext3 --label secondary 
--align 4 --size 125
part /data --ondisk mmcblk0 --fstype=ext3 --label data --align 4 --size 730

bootloader --timeout=0 --append="rootwait rootfstype=ext3 console=tty0"

and produced these 2 lines in fstab:
/dev/mmcblk0p3  /rescue ext3defaults0   0
/dev/mmcblk0p5  /data   ext3defaults0   0

If you provide more info about your setup(layers used?) I can try to
reproduce it and fix the issue.
Creating bug in https://bugzilla.yoctoproject.org would be great too.

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

Re: [linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs

2016-02-10 Thread Sullivan, California L 
On 02/07/2016 03:21 PM, Paul Gortmaker wrote:
> [[linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs] On 04/02/2016 (Thu 
> 16:25) California Sullivan wrote:
>
>> These options default to !EXPERT. Since we removed EXPERT from base,
>> these became enabled, adding functionality and size that we do not need.
> I wonder about the "do not need" part.  Nothing is more annoying than
> booting up something and then finding a USB keyboard isn't working
> because of some missing HID driver.  I am guessing that is the logic
> behind the !EXPERT default.
>
> Maybe we want to eat the size increase for standard users and toss the
> is not set values into tiny.cfg for those who are really keen on size?
>
> P.
> --
Funny you should say this. Somebody on the BSP team ran into this just
yesterday!
I agree with you. I'll remove this for v2 and probably send in a
standalone patch that enables more HIDs in base.

---
Cal Sullivan

>> Signed-off-by: California Sullivan 
>> ---
>>  ktypes/base/base.cfg | 11 +++
>>  1 file changed, 11 insertions(+)
>>
>> diff --git a/ktypes/base/base.cfg b/ktypes/base/base.cfg
>> index 30a3f77..f716fb3 100644
>> --- a/ktypes/base/base.cfg
>> +++ b/ktypes/base/base.cfg
>> @@ -791,6 +791,17 @@ CONFIG_WATCHDOG=y
>>  #
>>  # HID Devices
>>  #
>> +# CONFIG_HID_A4TECH is not set
>> +# CONFIG_HID_APPLE is not set
>> +# CONFIG_HID_BELKIN is not set
>> +# CONFIG_HID_CHERRY is not set
>> +# CONFIG_HID_CHICONY is not set
>> +# CONFIG_HID_CYPRESS is not set
>> +# CONFIG_HID_EZKEY is not set
>> +# CONFIG_HID_KENSINGTON is not set
>> +# CONFIG_HID_LOGITECH is not set
>> +# CONFIG_HID_MICROSOFT is not set
>> +# CONFIG_HID_MONTEREY is not set
>>  
>>  #
>>  # USB support
>> -- 
>> 2.5.0
>>
>> -- 
>> ___
>> linux-yocto mailing list
>> linux-yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/linux-yocto

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

Re: [yocto] wic: Setting partition id value?

2016-02-10 Thread Jon Szymaniak 
On Feb 10, 2016 12:24 PM, "Usman, Fahad"  wrote:
>
> Hi,
> Is there a way to create a partition with an arbitrary partition id,
using wic tool. We want to create a disk image using wic for Altera Cyclone
V. It require the partition id to be set to a particular hex value for the
partition it reads the boot loader binary from. The partition id does get
set automatically to the correct value depending on the value of fstype
(eg. 0x83 for ext3 or 0x0c for fat32), but I couldn't find a way to set it
to an arbitrary value.
>

I ran into this problem as well, but with parted. My hack was to use dd to
write the correct type ID into the image's MBR after I finished creating
the partitions on the image file.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto