[yocto] Meeting at FOSDEM
Hi all, Last year was my first trip to FOSDEM and I'm sending this for anyone involved with or interested in Yocto Project/OpenEmbedded who's in the same situation this year. Whilst it's easy to find people on Saturday/Sunday as they'll be at the OpenEmbedded/Yocto Project stall, it can be difficult to find people on the Friday evening if you've only spoke to them online and don't know what they look like in person. I'll be at the beer event this evening at the Delirium Cafe from around 7pm if travel goes to plan. I'd suggest any Yocto/OE folk gather just inside and to the left of the main doors into the Delirium Cafe at 8pm so that anyone new can find us easily. I'll try to keep up with my emails depending on wifi and mobile network quality. Drop me a message off the list if you'd like my mobile number to arrange meeting up. Many thanks, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk signature.asc Description: Digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] SPR issue while booting qemu for POWER PC ppce500v2
Hello, I am trying to perform LTP testing for POWER ppce500v2. I used the following rfs and kernel image for testing the LTP test prefix [cross build for ppce500ve using ppce500v2 custom toolchain] in QEMU system mode. http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/machines/qemu/qemuppc/core-image-sato-sdk-qemuppc.ext3 http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/machines/qemu/qemuppc/vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin When configured for '-M ppce500 -cpu e500v2' it gave me the following error, $ qemu-system-ppc -kernel vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin -net nic,model=pcnet -net tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu e500v2 -M ppce500 -hda core-image-base-qemuppc-20150112233527.rootfs.ext3 -no-reboot -show-cursor -no-reboot -nographic -m 512 --append "root=/dev/hda rw console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=512M console=ttyS0" Trying to write invalid spr 536 (0x218) 34c0 Any pointers or inputs/suggestions will be highly appreciated. Regards, Amruta!!! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SPR issue while booting qemu for POWER PC ppce500v2
I guess it has something to do with, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b813bdebb36501500e86fea5f7e15b4b15ea0902 https://bugzilla.yoctoproject.org/show_bug.cgi?id=6687 In other words, you should try with the latest images if any. On Fri, Jan 30, 2015 at 4:50 PM, amruuta ghatge wrote: > > Hello, > > I am trying to perform LTP testing for POWER ppce500v2. > > I used the following rfs and kernel image for testing the LTP test prefix > [cross build for ppce500ve using ppce500v2 custom toolchain] in QEMU system > mode. > > > http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/machines/qemu/qemuppc/core-image-sato-sdk-qemuppc.ext3 > > > > http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/machines/qemu/qemuppc/vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin > > When configured for '-M ppce500 -cpu e500v2' it gave me the following > error, > > $ qemu-system-ppc -kernel > vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin > -net nic,model=pcnet -net tap,vlan=0,ifname=tap0,script=no,downscript=no > -cpu e500v2 -M ppce500 -hda > core-image-base-qemuppc-20150112233527.rootfs.ext3 -no-reboot > -show-cursor -no-reboot -nographic -m 512 --append "root=/dev/hda rw > console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 > mem=512M console=ttyS0" > > Trying to write invalid spr 536 (0x218) 34c0 > > Any pointers or inputs/suggestions will be highly appreciated. > > Regards, > > Amruta!!! > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- JCP -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-toolchain-qt5] Can't install qtwebkit-dev-5.3.2-r0@i586: no package provides qtwebkit = 5.3.2-r0
TADA! well reading README helped ;), actually reading log.do_configure of
qtwebkit would help as well ;)
So after all, I set in qtbase.inc:
...
PACKAGECONFIG_ICU ?= "icu"
...
PACKAGECONFIG ?= " \
...
${PACKAGECONFIG_ICU} \
"
After that bitbake'ed meta-toolchain-qt5 again and voila! SDK .sh script
was generated alright
I have other problems now with Qt Creator compiling apps, but this will be
a story for another thread...
thank you (Martin)!
and best regards
simon:-)
On Wed, Jan 28, 2015 at 9:06 PM, Martin Jansa
wrote:
> On Wed, Jan 28, 2015 at 06:15:11PM +0100, Simon Bolek wrote:
> > hello group!
> >
> > working with dizzy trying to
> > *bitbake meta-toolchain-qt5*
> > it fails at the step
> >
> > *do_populate_sdk*
> >
> > with the error(see below). So if i read the error correctly, qtwebkit-dev
> > is missing qtwebkit.
> > There is no such package as qtwebkit beeing generated :( So is this a
> bug?
> > Or maybe I am doing sth wrong?
>
> Read README file and qtbase.inc about mandatory PACKAGECONFIG options.
>
> > HELP please :) Any hint would be more than welcome.
> > *BTW: Working with daisy did not produce such an error.*
> >
> > +++
> >
> >
> >
> >
> >
> >
> > *ERROR: Unable to install packages. Command
> > '/home/simon/poky-dizzy/build/tmp/sysroots/i686-linux/usr/bin/smart
> --quiet
> >
> --data-dir=/home/simon/poky-dizzy/build/tmp/work/i586-poky-linux/meta-toolchain-qt5/1.0-r0/sdk/image/opt/poky/1.7/sysroots/i586-poky-linux/var/lib/smart
> > install -y packagegroup-core-standalone-sdk-target-dbg@all
> > packagegroup-core-standalone-sdk-target@all
> > packagegroup-qt5-toolchain-target@all' returned 1:error: Can't install
> > qtwebkit-dev-5.3.2-r0@i586: no package provides qtwebkit =
> 5.3.2-r0ERROR:
> > Function failed: do_populate_sdkERROR: Logfile of failure stored in:
> >
> /home/simon/poky-dizzy/build/tmp/work/i586-poky-linux/meta-toolchain-qt5/1.0-r0/temp/log.do_populate_sdk.20827ERROR:
> > Task 7
> > (/home/simon/poky-dizzy/sources/meta-qt5/recipes-qt/meta/
> meta-toolchain-qt5.bb
> > , do_populate_sdk) failed with exit code
> '1'*
> > +++
> >
> > thank you and br
> > simon:)
>
> --
> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SPR issue while booting qemu for POWER PC ppce500v2
On 01/30/2015 06:20 AM, amruuta ghatge wrote: Hello, I am trying to perform LTP testing for POWER ppce500v2. I used the following rfs and kernel image for testing the LTP test prefix [cross build for ppce500ve using ppce500v2 custom toolchain] in QEMU system mode. http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/machines/qemu/qemuppc/core-image-sato-sdk-qemuppc.ext3 http://downloads.yoctoproject.org/releases/yocto/yocto-1.7/machines/qemu/qemuppc/vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin When configured for '-M ppce500 -cpu e500v2' it gave me the following error, $ qemu-system-ppc -kernel vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin -net nic,model=pcnet -net tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu e500v2 -M ppce500 -hda core-image-base-qemuppc-20150112233527.rootfs.ext3 -no-reboot -show-cursor -no-reboot -nographic -m 512 --append "root=/dev/hda rw console=ttyS0 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=512M console=ttyS0" Trying to write invalid spr 536 (0x218) 34c0 Maybe this will help - I just looked at both the E500 (includes V2) and E5500 reference manuals. I couldn't find the definition of an SPR 536. Could SPR 536 be specific to a particular SOC, or maybe it's just a typo in the code somewhere? Any pointers or inputs/suggestions will be highly appreciated. Regards, Amruta!!! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 1.7 - QtCreator ERROR while linking- /usr/bin/ld: cannot find /lib/libpthread.so.0 inside
hello! So after successfully bitbaking and installing meta-toolchain-st5 I set up QtCreator 3.2.2 and tried to compile an app against SDK of qt5. However I get an error: /usr/bin/ld: cannot find /lib/libpthread.so.0 inside /usr/bin/ld: cannot find /usr/lib/libpthread_nonshared.a inside libpthread.so is available alright, but the linker is not finding it somehow. LD variable is set to: i586-poky-linux-ld --sysroot=/opt/poky/1.7/sysroots/i586-poky-linux Maybe this is a pure QtCreator bug, but where would I set(override) the linker correctly? Any suggestions? If i run(from console ): i586-poky-linux-ld --sysroot=/opt/poky/1.7/sysroots/i586-poky-linux /opt/poky/1.7/sysroots/i586-poky-linux/usr/lib/libpthread.so it is fine(it gives me some warning, but no errors). Here are the QtCreator settings for Qt5 Kit: GCC Compiler: path: /opt/poky/1.7/sysroots/i686-pokysdk-linux/usr/bin/i586-poky-linux/i586-poky-linux-gcc Qt Version: qmake location: /opt/poky/1.7/sysroots/i686-pokysdk-linux/usr/bin/qt5/qmake Qt Kit: sysroot: /opt/poky/1.7/sysroots/i586-poky-linux compiler: set to above gcc compiler qt version: set to above qt version even manually setting LIBS to LIBS += -L//opt/poky/1.7/sysroots/i586-poky-linux/lib or LIBS += -L//opt/poky/1.7/sysroots/i586-poky-linux/usr/lib does not help(but i really do not think this is the problem). So you have any hints for me? I compared the settings of 1.6.1, and there is no difference as far as my eye can catch. PS. I switched from 1.6.1 to 1.7, becasue of gclib not beeing available in 1.6.1. cheers simon :-) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto-custom kernel build issue
Hi, I am new to yocto project build system. I downloaded the yocto project build system from git. I built for the all qemu architectures(MIPS,ARM,PPC,X86) and ran on qemu. all are working fine. Now I need to create a bsp layer for my board which has the mips processor core. I created the bsp layer with using the yocto-bsp create command. here I use the my own kernel which is reside at our local git repositery. I gave this path while creating the bsplayer. After adding my bsp layer to bblayers and my mechine to local.conf i built the kernel using bitbake -k core-image-minimal command. While building i got the following errors: Log data follows: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | NOTE: make oldnoconfig | make: *** No rule to make target `oldnoconfig'. Stop. | NOTE: make oldconfig | make: *** No rule to make target `oldconfig'. Stop. | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+12bbf6468e-r0/temp/log.do_configure.14044) And also i did not got "src" folder in the following path for my mechine which is there for the qemu mips. /home/testuser/poky/build/tmp/sysroots/mydhanush/usr could you please help for resolving this issue. thanks in advance. Thanks & Regards, Raghavendra K. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto-custom kernel build issue
On 15-01-30 09:08 AM, Raghavendra Kakarla wrote:
Hi,
I am new to yocto project build system. I downloaded the yocto project build
system from git. I built for the all qemu architectures(MIPS,ARM,PPC,X86) and
ran on qemu.
all are working fine.
Now I need to create a bsp layer for my board which has the mips processor core.
I created the bsp layer with using the yocto-bsp create command.
here I use the my own kernel which is reside at our local git repositery. I
gave this path while creating the bsplayer.
After adding my bsp layer to bblayers and my mechine to local.conf i built the
kernel using bitbake -k core-image-minimal command.
While building i got the following errors:
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make oldnoconfig
| make: *** No rule to make target `oldnoconfig'. Stop.
| NOTE: make oldconfig
| make: *** No rule to make target `oldconfig'. Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+12bbf6468e-r0/temp/log.do_configure.14044)
And also i did not got "src" folder in the following path for my mechine which
is there for the qemu mips.
/home/testuser/poky/build/tmp/sysroots/mydhanush/usr
Is the source directory in
/home/testuser/poky/build/tmp/work-shared//kernel-source ?
And if so, is your recipe setting ${S} in any way ?
Bruce
could you please help for resolving this issue.
thanks in advance.
Thanks & Regards,
Raghavendra K.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding 'sbin' to default path
Hi, Why does the PATH variable in the dot.bashrc shipped by the base-files not include 'sbin' paths? It seems like any interactive user should be able to call e.g. 'ifconfig' informationally---they should, and would still be, blocked from calling 'ifconfig eth0 up' After looking at the PATH for a generic user on my local Ubuntu system, I just added a patch to my meta layer to add the following line to the dot.bashrc: export PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin It seems to work well---users created with the extrauser class pull this default from the skel. As this is security related though, I wanted to ask the question to make sure I'm not doing something silly, dangerous or otherwise idiotic. Thanks, --Ash -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [oe] [meta-raspberrypi][PATCH v2] qtbase: Add basic Qt5 building support
Hello,
On Tue, Jan 27, 2015 at 02:26:55PM +0800, Yen-Chin Lee wrote:
> To build raspberrypi with Qt5, we need to add extra QT_CONFIG_FLAGS to
> indicate device config.
>
> Signed-off-by: Yen-Chin Lee
> ---
> qt5-layer/recipes-qt/qt5/qtbase_%.bbappend | 7 +++
> 1 file changed, 7 insertions(+)
> create mode 100644 qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
>
> diff --git a/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
> b/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
> new file mode 100644
> index 000..384df9f
> --- /dev/null
> +++ b/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
> @@ -0,0 +1,7 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +QT_CONFIG_FLAGS_append_raspberrypi = " \
> +-device linux-rasp-pi-g++ \
> +-device-option CROSS_COMPILE=${TARGET_PREFIX} \
> +-I${STAGING_DIR_TARGET}${includedir}/interface/vcos/pthreads \
> +"
> --
> 1.9.3 (Apple Git-50)
>
> --
> ___
> Openembedded-devel mailing list
> openembedded-de...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
First of all please send patches to meta-raspberrypi mailing list (yocto).
Use README for additional information.
For whatever reason I can't bake qtbase:
pulse/pulseaudio.h: No such file or directory
| #include
| ^
| compilation terminated.
| Makefile:206: recipe for target 'pulseaudio.o' failed
| make: *** [pulseaudio.o] Error 1
| PulseAudio disabled.
| PulseAudio support cannot be enabled due to functionality tests!
Any idea why? Didn't you encounter this issue?
--
Andrei Gherzan
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] ustr: fix typo in SRC_URI
From: Armin Kuster
This fixes
ERROR: Fetcher failure: Fetch command failed with exit code 8, output:
http://www.and.org/ustr/$%7BBPV%7D/ustr-1.0.4.tar.bz2:
2015-01-30 18:26:38 ERROR 404: Not Found.
Changed "BPV" to "PV"
Signed-off-by: Armin Kuster
---
recipes-extended/ustr/ustr_1.0.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-extended/ustr/ustr_1.0.4.bb
b/recipes-extended/ustr/ustr_1.0.4.bb
index a0a1e41..cdb78ad 100644
--- a/recipes-extended/ustr/ustr_1.0.4.bb
+++ b/recipes-extended/ustr/ustr_1.0.4.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=c79c6e2ae13418d16d7dc82df960a1e7 \
file://LICENSE_MIT;md5=c61e779b782608472bd87593c3c3916f"
SRC_URI = "\
-http://www.and.org/ustr/${BPV}/${BPN}-${PV}.tar.bz2 \
+http://www.and.org/ustr/${PV}/${BPN}-${PV}.tar.bz2 \
file://ustr-makefile-fix.patch;patch=1 \
file://ustr-fix__va_copy-not-defined.patch;patch=2 \
file://ustr-c99-inline.patch;patch=3"
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] samhain: fix aarch64 build issues
Signed-off-by: Armin Kuster
---
.../samhain/files/add_aarch64_to_configure.patch | 34 ++
recipes-security/samhain/samhain.inc | 5
2 files changed, 39 insertions(+)
create mode 100644
recipes-security/samhain/files/add_aarch64_to_configure.patch
diff --git a/recipes-security/samhain/files/add_aarch64_to_configure.patch
b/recipes-security/samhain/files/add_aarch64_to_configure.patch
new file mode 100644
index 000..05f4413
--- /dev/null
+++ b/recipes-security/samhain/files/add_aarch64_to_configure.patch
@@ -0,0 +1,34 @@
+Index: samhain-3.1.3/config.sub
+===
+--- samhain-3.1.3.orig/config.sub
samhain-3.1.3/config.sub
+@@ -250,6 +250,7 @@ case $basic_machine in
+ | alpha64 | alpha64ev[4-8] | alpha64ev56 | alpha64ev6[78] |
alpha64pca5[67] \
+ | am33_2.0 \
+ | arc | arm | arm[bl]e | arme[lb] | armv[2345] | armv[345][lb] | avr |
avr32 \
++| aarch64 | aarch64be \
+ | bfin \
+ | c4x | clipper \
+ | d10v | d30v | dlx | dsp16xx \
+@@ -332,6 +333,7 @@ case $basic_machine in
+ | alpha64-* | alpha64ev[4-8]-* | alpha64ev56-* | alpha64ev6[78]-* \
+ | alphapca5[67]-* | alpha64pca5[67]-* | arc-* \
+ | arm-* | armbe-* | armle-* | armeb-* | armv*-* \
++| aarch64-* | aarch64be-* \
+ | avr-* | avr32-* \
+ | bfin-* | bs2000-* \
+ | c[123]* | c30-* | [cjt]90-* | c4x-* | c54x-* | c55x-* | c6x-* \
+Index: samhain-3.1.3/config.guess
+===
+--- samhain-3.1.3.orig/config.guess
samhain-3.1.3/config.guess
+@@ -882,6 +882,9 @@ EOF
+ echo ${UNAME_MACHINE}-unknown-linux-gnueabi
+ fi
+ exit ;;
++aarch64*:Linux:*:*)
++ echo ${UNAME_MACHINE}-unknown-linux-gnu
++ exit ;;
+ avr32*:Linux:*:*)
+ echo ${UNAME_MACHINE}-unknown-linux-gnu
+ exit ;;
diff --git a/recipes-security/samhain/samhain.inc
b/recipes-security/samhain/samhain.inc
index b914cb1..3c54c28 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=8ca43cbc842c2336e835926c2166c28b"
SRC_URI = "http://la-samhna.de/archive/samhain_signed-${PV}.tar.gz \
file://${INITSCRIPT_NAME}.init \
file://${INITSCRIPT_NAME}.default \
+ file://add_aarch64_to_configure.patch \
"
SRC_URI[md5sum] = "64572a4dbfdc8065d6e9f7ca0eab0a34"
@@ -41,6 +42,10 @@ do_configure_prepend_arm() {
export sh_cv___va_copy=yes
}
+do_configure_prepend_aarch64() {
+export sh_cv___va_copy=yes
+}
+
# If we use oe_runconf in do_configure() it will by default
# use the prefix --oldincludedir=/usr/include which is not
# recognized by Samhain's configure script and would invariably
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
