[yocto] Public key for U-Boot verified boot is not inserted in DTB when rebuilding from sstate

[Andersen, Christian]

Hello,

I have a problem with U-Boot verified boot and the sstate caching of build 
artifacts.

On a clean rebuild (deleted sstate and tmp dir), the signed FIT image and 
U-Boot incl. the public key are correctly created.
But when I delete the tmp dir and let bitbake recreate it from sstate, the 
public key in U-Boot is missing.

The task sequence according to uboot-sign.bbclass is:

#   u-boot:do_deploy_dtb
#   u-boot:do_deploy
#   virtual/kernel:do_assemble_fitimage
#   u-boot:do_concat_dtb
#   u-boot:do_install

The problem seems to be that while assembling the FIT image (from the kernel 
recipe), the U-Boot DTB in DEPLOY_IMAGE_DIR is modified and the public key is 
inserted. After that U-Boot and the new DTB are concatenated. This happens for 
the U-Boot image in DEPLOYDIR as well in DEPLOY_IMAGE_DIR.

The problem now is, that the sstate caches the versions of U-Boot and DTB while 
deploying it. Since this happens before assembling the FIT image, the sstate 
now contains U-Boot and DTB without the public key.

U-Boot unfortunately (silently!) disables verified boot when the public key is 
not available in the DTB.

I already filed a bug (#12112) for this, but has anybody an idea how to easily 
fix this (other than cleaning the sstate of U-Boot/Kernel after deleting the 
tmp dir)?

A possible solution would be to remove the dependency between kernel and 
U-Boot. But in this case it would be necessary to insert the public key into 
the DTB while building U-Boot without using the FIT image from the kernel 
build. Unfortunately uboot-mkimage does not support this at the moment.


Regards
Christian

-- 
KOSTAL Industrie Elektrik GmbH
www.kostal-industrie-elektrik.com


KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Dr.-Ing. Dipl.-Wirt.Ing. Manfred Gerhard, Dipl.-Ing. Marwin 
Kinzl, Dipl.-Oec. Andreas Kostal

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

[yocto] Building multiple FIT images with different initramfs images

[Andersen, Christian]

Hello,

we are using signed FIT images to establish a verified boot system. Now I try 
to generate multiple FIT images, where every image contains another initramfs. 
The idea is to use a signed FIT image (loaded via TFTP) including a special 
ramdisk in our production line. This ramdisk only contains the code to copy the 
rootfs onto our eMMC. Another FIT image (the default one) will be included in 
our rootfs and used in all other cases (in the field).

Currently Yocto (kernel-fitimage.bbclass) only supports the variable 
INITRAMFS_IMAGE (which as far as I know, has to be set in the machine config). 
So I am not able to build a second FIT image with another initramfs image.

I did some (ugly) hacking on kernel.bbclass and kernel-fitimage.bbclass and 
created a new variable INITRAMFS_IMAGES, which may contain one or more 
different initramfs images. Using this approach I am now able to build multiple 
FIT images for one machine, which contain different ramdisks.

What do you think about such a feature? Is it something which might be 
integrated into mainline YP/OE?

Regards
Christian


KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Dr.-Ing. Dipl.-Wirt.Ing. Manfred Gerhard, Dipl.-Ing. Marwin 
Kinzl, Dipl.-Oec. Andreas Kostal

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

[yocto] GPG signed package feeds and packages: opkg update fails with "No public key"

[Andersen, Christian]

Hello,

I am trying to sign our ipk-packages and the package feed using GPG. As far as 
I can tell the signatures are correctly generated using this in the local.conf:

INHERIT += "sign_package_feed sign_ipk"
PACKAGE_FEED_GPG_NAME ?= "73CE8000"
PACKAGE_FEED_GPG_PASSPHRASE_FILE ?= "/var/lib/jenkins/.gnupg/passwd.txt"
IPK_GPG_NAME ?= "73CE8000"
IPK_GPG_PASSPHRASE_FILE ?= "/var/lib/jenkins/.gnupg/passwd.txt"
GPG_PATH ?= "/var/lib/jenkins/.gnupg"

The public key is installed using opkg-keyrings and this config:

OPKG_KEYRING_KEYS = "73CE8000"

On the target I am able to verify that the public key is available:

root@scb-anders05:~# opkg-key list
/etc/opkg/trusted.gpg
-
pub   rsa2048 2017-08-04 [SC]
  B104E37136084E68203BB2CD5676B9F373CE8000
uid   [unknown] Company 
sub   rsa2048 2017-08-04 [E]

The opkg.conf contains:

option check_signature 1
#option check_pkg_signature 1
option signature_type gpg-asc

But when I try opkg update I get:

root@scb-anders05:~# opkg update
Downloading http://internalhost:8000/puck/pyro-develop/ipk/all/Packages.gz.
Downloading http://internalhost:8000/puck/pyro-develop/ipk/all/Packages.asc.
Downloading 
http://internalhost:8000/puck/pyro-develop/ipk/cortexa8hf-neon/Packages.gz.
Downloading 
http://internalhost:8000/puck/pyro-develop/ipk/cortexa8hf-neon/Packages.asc.
Downloading http://internalhost:8000/puck/pyro-develop/ipk/scb/Packages.gz.
Downloading http://internalhost:8000/puck/pyro-develop/ipk/scb/Packages.asc.
Collected errors:
* opkg_verify_gpg_signature: Signature status returned error: No public key
* pkg_src_verify: Signature verification failed for all.
* opkg_verify_gpg_signature: Signature status returned error: No public key
* pkg_src_verify: Signature verification failed for cortexa8hf-neon.
* opkg_verify_gpg_signature: Signature status returned error: No public key
* pkg_src_verify: Signature verification failed for scb.

When manually loading the Packages and Packages.asc and verify the signature on 
the target it seems to work:

root@scb-anders05:~# opkg-key adv --verify Packages.asc Packages
Executing: gpg --no-options --no-default-keyring --keyring 
/etc/opkg/trusted.gpg --secret-keyring /etc/opkg/secring.gpg --trustdb-name 
/etc/opkg/trustdb.gpg --verify Packages.asc Packages
gpg: Signature made Fri Aug  4 17:00:52 2017 CEST
gpg:using RSA key 5676B9F373CE8000
gpg: Good signature from "Company " [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: B104 E371 3608 4E68 203B  B2CD 5676 B9F3 73CE 8000

Even after changing the trust-level for the public key to 5 (ultimate), opkg 
update does not accept the signature.

Does anybody have an idea what's going on and how I can fix this?

Regards
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Dr.-Ing. Dipl.-Wirt.Ing. Manfred Gerhard, Dipl.-Ing. Marwin 
Kinzl, Dipl.-Oec. Andreas Kostal

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

Re: [yocto] postinstall intercept hooks fail because of missing qemuwrapper

[Andersen, Christian]

Hi Markus,

thanks for the hint. In my image recipe I was setting some other dependencies 
for wic using DEPENDS="...". So the dependency for qemuwrapper-cross, which is 
provided by image.bbclass, was overwritten. After changing my dependencies to 
DEPENDS_append it is working now.

Regards
Christian


> -Ursprüngliche Nachricht-
> Von: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> Im Auftrag von Markus Volk
> Gesendet: Mittwoch, 2. August 2017 11:36
> An: yocto@yoctoproject.org
> Betreff: Re: [yocto] postinstall intercept hooks fail because of missing
> qemuwrapper
> 
> hi,
> 
> this could be fixed by adding "qemuwrapper-cross" to the depends of your
> image.bb
> 
> regards
> Markus
> 
> On Wed, 2 Aug 2017 09:24:06 +
> "Andersen, Christian" <c.ander...@kostal.com> wrote:
> 
> > Hello,
> >
> > we are using the current version of pyro. When building an image recipe we 
> > get
> some warnings, that some postinstall intercept hooks failed. The log-file of
> do_rootfs shows:
> >
> >(...)
> >
> > So qemuwrapper is missing. How can I fix this?
> >
> > Kind regards
> > Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Dr.-Ing. Dipl.-Wirt.Ing. Manfred Gerhard, Dipl.-Ing. Marwin 
Kinzl, Dipl.-Oec. Andreas Kostal

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

[yocto] postinstall intercept hooks fail because of missing qemuwrapper

[Andersen, Christian]

Hello,

we are using the current version of pyro. When building an image recipe we get 
some warnings, that some postinstall intercept hooks failed. The log-file of 
do_rootfs shows:

NOTE: Running intercept scripts:
NOTE: > Executing update_gio_module_cache intercept ...
/home/anders05/Dev/build-puck/build/tmp/work/abc-def-linux-gnueabi/puck-image-basic/1.0-r0/intercept_scripts/update_gio_module_cache:
 9: 
/home/anders05/Dev/build-puck/build/tmp/work/abc-def-linux-gnueabi/puck-image-basic/1.0-r0/intercept_scripts/update_gio_module_cache:
 qemuwrapper: not found
WARNING: The postinstall intercept hook 'update_gio_module_cache' failed (exit 
code: 127)! See log for details! (Output: b'')
WARNING: The postinstalls for the following packages will be postponed for 
first boot: libglib-2.0-0
NOTE: > Executing update_font_cache intercept ...
/home/anders05/Dev/build-puck/build/tmp/work/abc-def-linux-gnueabi/puck-image-basic/1.0-r0/intercept_scripts/update_font_cache:
 11: 
/home/anders05/Dev/build-puck/build/tmp/work/abc-def-linux-gnueabi/puck-image-basic/1.0-r0/intercept_scripts/update_font_cache:
 qemuwrapper: not found
WARNING: The postinstall intercept hook 'update_font_cache' failed (exit code: 
127)! See log for details! (Output: b'')
WARNING: The postinstalls for the following packages will be postponed for 
first boot: ttf-sazanami-mincho ttf-arphic-uming ttf-dejavu-sans 
ttf-dejavu-sans-mono ttf-devanagari

So qemuwrapper is missing. How can I fix this?

Kind regards
Christian


KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Dr.-Ing. Dipl.-Wirt.Ing. Manfred Gerhard, Dipl.-Ing. Marwin 
Kinzl, Dipl.-Oec. Andreas Kostal

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

Re: [yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Hi Laurent,

> In pyro the creation of users and group (using the useradd class) is done 
> during
> the package pre-installation.
> 
> So my best guess is that you could move the owner/group change in the package
> post-installation as follows:

thanks for your advice. Currently it seems - as stated by Maxim B. John - do be 
a bug / regression in pyro, so adding shadow-native to the dependencies helps. 
Besides that I think that it is okay to access the user in the install task, 
since it should already be available then.

Regards
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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

Re: [yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Hi Maxin,

> > Do I have to add shadow-native in all these recipes or is it a bug / 
> > regression in
> pyro?
> 
> It is one of those "known" limitations which fell through the cracks.
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8078
> 
> Thanks for bringing this up. We need to address this for pyro/master.

okay, thanks, so I am adding shadow-native as a workaround for the moment.

Regards
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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

Re: [yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Hi Maxin,

> Here, could you try to build again with an additional DEPENDENCY on shadow-
> native:
> ie: instead of
> >DEPENDS = "puck-base"
> DEPENDS = "puck-base shadow-native"
> 
> To be sure, please cleansstate the puck-base and test before build.

Thanks! I tried as you suggested (cleansstate and then build) and with 
shadow-native it is working now.
 
Do I have to add shadow-native in all these recipes or is it a bug / regression 
in pyro?

Regards,
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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

[yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Any ideas how to use "useradd" bbclass with pyro?

If I move useradd to my recipe my-appl.bb, it works. But there are more recipes 
depending on the added user, so I want to add this user in a base-recipe and 
just depend on it using (DEPENDS/RDEPENDS).

Regards
Christian

Von: Andersen, Christian
Gesendet: Dienstag, 13. Juni 2017 18:10
An: 'yocto@yoctoproject.org' <yocto@yoctoproject.org>
Betreff: useradd and one sysroot per recipe in pyro

Hello,

currently I am trying the newest Yocto release (pyro). It seems I have a 
problem with useradd and the new concept of one sysroot per recipe.

I have a base recipe (let's call it my-base.bb) which inherits useradd and 
creates a new user (let's call him myuser):

inherit useradd

USERADD_PACKAGES = "${PN}"
USERADD_PARAM_${PN} = " \
--uid 1200 \
--gid 1200 \
--system \
--shell /bin/bash \
--create-home \
--home-dir /home/myuser \
--groups mygroup,video,input \
myuser"
GROUPADD_PARAM_${PN} = "-g 1200 mygroup"

do_install () {
install -d ${D}/home/myuser
chown -R myuser:mygroup ${D}/home/myuser
}

Other recipes depend on this base recipe (via DEPENDS and RDEPENDS), because 
they require this user, e.g. in recipe my-appl.bb (in this case python only, so 
no configure or compile):

DEPENDS = "puck-base"
RDEPENDS_${PN} = "puck-base python3-dbus python3-sqlite3 python3-netclient 
python3-requests"

do_configure[noexec] = "1"
do_compile[noexec] = "1"

do_install () {
(...)

install -d ${D}${sysconfdir}/myappl
chown -R myuser:mygroup ${D}${sysconfdir}/myappl

install -d ${D}${localstatedir}/lib/myappl
chown -R myuser:mygroup ${D}${localstatedir}/lib/myappl
}

Unfortunately I get an error when building the recipe my-appl.bb

| chown: invalid user: 'myuser:mygroup'
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at ...)
ERROR: Task (.../my-appl.bb:do_install) failed with exit code '1'

In morty the user was created in the shared sysroot. But using pyro the user is 
not created in the recipe-sysroot.

What am I doing wrong and is there a way to solve this?

Thanks in advance!

Regards
Christian

KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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

[yocto] useradd and one sysroot per recipe in pyro

[Andersen, Christian]

Hello,

currently I am trying the newest Yocto release (pyro). It seems I have a 
problem with useradd and the new concept of one sysroot per recipe.

I have a base recipe (let's call it my-base.bb) which inherits useradd and 
creates a new user (let's call him myuser):

inherit useradd

USERADD_PACKAGES = "${PN}"
USERADD_PARAM_${PN} = " \
--uid 1200 \
--gid 1200 \
--system \
--shell /bin/bash \
--create-home \
--home-dir /home/myuser \
--groups mygroup,video,input \
myuser"
GROUPADD_PARAM_${PN} = "-g 1200 mygroup"

do_install () {
install -d ${D}/home/myuser
chown -R myuser:mygroup ${D}/home/myuser
}

Other recipes depend on this base recipe (via DEPENDS and RDEPENDS), because 
they require this user, e.g. in recipe my-appl.bb (in this case python only, so 
no configure or compile):

DEPENDS = "puck-base"
RDEPENDS_${PN} = "puck-base python3-dbus python3-sqlite3 python3-netclient 
python3-requests"

do_configure[noexec] = "1"
do_compile[noexec] = "1"

do_install () {
(...)

install -d ${D}${sysconfdir}/myappl
chown -R myuser:mygroup ${D}${sysconfdir}/myappl

install -d ${D}${localstatedir}/lib/myappl
chown -R myuser:mygroup ${D}${localstatedir}/lib/myappl
}

Unfortunately I get an error when building the recipe my-appl.bb

| chown: invalid user: 'myuser:mygroup'
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at ...)
ERROR: Task (.../my-appl.bb:do_install) failed with exit code '1'

In morty the user was created in the shared sysroot. But using pyro the user is 
not created in the recipe-sysroot.

What am I doing wrong and is there a way to solve this?

Thanks in advance!

Kind regards

KOSTAL Industrie Elektrik GmbH

B.Sc.
Christian Andersen
IE1.3 Entwicklung Desktop-/Webanwendungen

Lange Eck 11, 58099 Hagen
Telefon: +49 2331 8040 - 634
Telefax: +49 2331 8040 - 660
E-Mail: c.ander...@kostal.com

Internet: 
http://www.kostal-industrie-elektrik.com



KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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

[yocto] vmdk and IMAGE_ROOTFS_EXTRA_SPACE?

[Andersen, Christian]

Hello,

is there a way to add some extra space to the rootfs in a vmdk image? It looks 
like the option IMAGE_ROOTFS_EXTRA_SPACE is only used by image.bbclass, but not 
by image-vm.bbclass.

Kind regards
Christian Andersen


KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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

Re: [yocto] Trouble with yocto sdk in collaboration with eclipse and cmake

[Andersen, Christian]

Hi,

>> On Jul 29, 2016, at 1:27 AM, Hartwig, Guido  wrote:
>>
>> Hi,
>> I have some trouble with the yocto sdk in collaboration with eclipse and 
>> yocto CMake project. I have install all necessary eclipse plugins and linked 
>> my sdk with the yocto-plugin as described in the manual. When I try to build 
>> the "Hello World" yocto cmake project it fails with following message:
>>
>> ..
>> CMake Error at
>> /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): The C 
>> compiler 
>> "/opt/puck/1.0.0/sysroots/x86_64-pucksdk-linux/usr/bin/arm-kostal-linux-gnueabi/arm-kostal-linux-gnueabi-gcc"
>>  is not able to compile a simple test program ...
>>
>> This error occurs because the compiler is called with the wrong flags.

the error seems to be already fixed in the eclipse-poky repository. Commit 
#8315d3ec84 to luna/krogoth branch:

org.yocto.sdk.ide: Use CFLAGS from CC variable in cmake toolchain file
The CC and CXX variables imported from the Yocto build environment
may contain additional compiler flags after the compiler name. Extract
those and add them to cmake toolchain file variables, too.

This is the exact issue we have seen. Unfortunately this change has been 
commited after the tag for yocto-2.1 was created and so this is not released 
yet. After building a new version of the eclipse plugin based on the 
luna/krogoth branch the error mentioned above is gone.

Regards
Christian


KOSTAL Industrie Elektrik GmbH - Sitz Lüdenscheid, Registergericht Iserlohn HRB 
3924 - USt-Id-Nr./Vat No.: DE 813742170
Postanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: +49  2351 
16-0 * Telefax: +49  2351 16-2400
Werksanschrift: Lange Eck 11, D-58099 Hagen * Tel. +49 2331 8040-601 * Fax +49 
2331 8040-602
Geschäftsführung: Axel Zimmermann, Dipl.-Ing. Marwin Kinzl, Dipl.-Oec. Andreas 
Kostal

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