[yocto] Antwort: Where to find the udevadm monitor?

[S . Jaritz]

I figured out.

udevadm monitor ist provided by the SystemV package.

Problem solved!

Stefan 


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:s.jar...@esa-grimma.de
An: yocto@yoctoproject.org
Datum:  18.10.2017 11:42
Betreff:[yocto] Where to find the udevadm monitor?
Gesendet von:   yocto-boun...@yoctoproject.org



Hej, 

Actually I am playing a bit arround with udev rules. For that I like to 
use the udevadm monitor. The udev is provided by 

/meta/recipes-core/udev/eudev_3.2.2.bb 

In this recipe there is no udevadm option. While checking, I saw it was 
once in udev-utils and been moved to udev.inc. 

https://patchwork.openembedded.org/patch/73987/ 

Since then udev has been replaced with eudev. Seems that udevadm got 
"lost" by the move from udev to eudev - or it went to an other recipe. 

My question is: 

Where to find a recipe containing udevadm/what options I need to set to 
include this program? 

Regards 

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
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] Where to find the udevadm monitor?

[S . Jaritz]

Hej,

Actually I am playing a bit arround with udev rules. For that I like to 
use the udevadm monitor. The udev is provided by 

/meta/recipes-core/udev/eudev_3.2.2.bb

In this recipe there is no udevadm option. While checking, I saw it was 
once in udev-utils and been moved to udev.inc.

https://patchwork.openembedded.org/patch/73987/

Since then udev has been replaced with eudev. Seems that udevadm got 
"lost" by the move from udev to eudev - or it went to an other recipe.

My question is:

Where to find a recipe containing udevadm/what options I need to set to 
include this program?

Regards

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: How to make changes and build u-boot source code in yocto

[S . Jaritz]

Hej ho

my Workflow for adjusting uboot (u-boot-at91):

1.) build the original uboot
2.) apply changes
3.) create patch
3.1.) if you reconfigure it -> save/copy the config
3.2.) if you adding code -> use meld or something similar to create a 
patch
4.) create u-boot-at91_%.bbappend
4.1) copy patch/config into that recipe dir
4.2) check u-boot-at91_%.bbappend paths etc.
5.) rebuild 

I you mess to much around in /tmp/work*** you should use "-c clean"/"-c 
cleanall" to reset it

regards

Stefan

ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Prasoon Kumar 
An: yocto@yoctoproject.org
Datum:  03.07.2017 08:34
Betreff:[yocto] How to make changes and build u-boot source code 
in yocto
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

I am trying to make some changes in u-boot code and using bitbake u-boot 
to build. But it doesn't build.
I also tried bitbake u-boot -c compile and bitbake u-boot deploy. This 
also didn't work.

Can I Get some help on how to change and build u-boot. 

Thanks,
Prasoon-- 
___
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] [meta-raspberrypi] How to add a own dts file and patch the dts makefile

[S . Jaritz]

Hej

It's friday and I have some time to play a bit around. I like to build a 
simple test-adapter using a RPi. I want to connect some of the 40GPIO pins 
with a custom mainboard. For that I like to define the pin behaviour by an 
own dts file.

I created my own dts file (testboard.dts) + a simple patch for 
"arch/arm/boot/dts/Makefile" to add the file.

For adding them into the build-process I am append the kernel build 
(linux-raspberrypi%.bbappend).

Now I have problems bringing them together, because the name of the 
git/source links changes (git -> linux-raspberrypi2-standard-build/source 
). Maybe some one has an idea?

I put the listings of the files below:

## linux-raspberrypi%.bbappend ##
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

SRC_URI += "file://testboard.dts
;subdir=linux-raspberrypi2-standard-build/source/arch/arm/boot/dts \
file://0001-add-testboard-to-makefile.patch \
"
PACKAGE_ARCH = "raspberrypi2"

KERNEL_DEVICETREE += "testboard.dtb"
#

## 0001-add-testboard-to-makefile.patch ##
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile

@@ -1,4 +1,8 @@
 ifeq ($(CONFIG_OF),y)
+
+# my own dts files
+dtb-$(CONFIG_ARCH_BCM2835) += \
+   testboard.dts
 
 dtb-$(CONFIG_ARCH_BCM2835) += \
bcm2708-rpi-b.dtb \
#

## testboard.dts ##
/dts-v1/;
#include "bcm2836.dtsi"
#include "bcm2835-rpi.dtsi"
#include "bcm283x-rpi-smsc9514.dtsi"
#include "bcm283x-rpi-usb-host.dtsi"

/ {
compatible = "raspberrypi,2-model-b", "brcm,bcm2836";
model = "RPi test";

memory {
reg = <0 0x4000>;
};

leds {
act {
gpios = < 47 0>;
};

pwr {
label = "PWR";
gpios = < 35 0>;
default-state = "keep";
linux,default-trigger = "default-on";
};
};

};

 {
pinctrl-0 = <  _alt0>;

/* I2S interface */
i2s_alt0: i2s_alt0 {
brcm,pins = <18 19 20 21>;
brcm,function = ;
status = "disabled";
};

cord0: cord0 {
brcm,pins = <5 6 25>;
brcm,function = ;
status = "okay";
};

};

 {
hpd-gpios = < 46 GPIO_ACTIVE_LOW>;
status = "disabled";
};
#

For that I put a question on stackoverflow:
https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

Regards form Germany!

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to setup apt-get to work togehter with the packages build with yocto?

[S . Jaritz]

Hej

I like to setup a central host for the packages build with yocto. The goal 
is, that everyone can download the "new" packages from a server in the 
local network. I am looking for a description how to archive that or some 
tips to start from.

Regards!

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to setup syslog by using an own filterfile and log policy configuration?

[S . Jaritz]

Hej

I like to configure syslog. It seems that are more than one way to set up 
syslog. I am asking for the comon way/steps to do that.

I have several use cases. To simplify I like to ask how to configure 
syslog to write an infinity long log file in /var/log/.

Following steps:
1.) configure what messages
1.1) create own "syslog.conf" (define /var/log/myLog)
1.2) append it to "recipes-core/busybox"

2.) configure how to log
??

I found two possible places to do that:
@meta-poky
-> "meta-poky/recipes-core/busybox/busybox/poky-tiny/defconfig"
###
#
# System Logging Utilities
#
CONFIG_SYSLOGD=y
CONFIG_FEATURE_ROTATE_LOGFILE=y
CONFIG_FEATURE_REMOTE_LOG=y
CONFIG_FEATURE_SYSLOGD_DUP=y
CONFIG_FEATURE_SYSLOGD_CFG=y
CONFIG_FEATURE_SYSLOGD_READ_BUFFER_SIZE=256
CONFIG_FEATURE_IPC_SYSLOG=y
CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE=16
CONFIG_LOGREAD=y
CONFIG_FEATURE_LOGREAD_REDUCED_LOCKING=y
CONFIG_KLOGD=y
CONFIG_FEATURE_KLOGD_KLOGCTL=y
CONFIG_LOGGER=y
###

>> add/change
"CONFIG_FEATURE_ROTATE_LOGFILE=n" by adding that line to 
meta-mylayer/conf/layer.conf"
etc.
???

@ "/etc/syslog-startup.conf"
###
# This configuration file is used by the busybox syslog init script,
# /etc/init.d/syslog[.busybox] to set syslog configuration at start time.

DESTINATION=file# log destinations (buffer file remote)
LOGFILE=/var/log/messages   # where to log (file)
REMOTE=loghost:514  # where to log (syslog remote)
REDUCE=no   # reduce-size logging
DROPDUPLICATES=no   # whether to drop duplicate log entries
#ROTATESIZE=0   # rotate log if grown beyond X [kByte]
#ROTATEGENS=3   # keep X generations of rotated logs
BUFFERSIZE=64   # size of circular buffer [kByte]
FOREGROUND=no   # run in foreground (don't use!)
#LOGLEVEL=5 # local log level (between 1 and 8)
###

In the systemV init script "/etc/init.d/syslog.bussybox" the file 
"/etc/syslog-startup.con" is read and used for configuration.

System behaviour:

When running my system, the log wraps when the logfile reaches 200kBytes. 
One logfile + one log-rotate file is generated.

Any ideas how to archive that syslog writes an infinite long log-file? 

I am working on the Yocto krogoth branch + meta-atmel / meta_openembedded 
(@ krogoth too).

Best regards,

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to create an user bsp based on a other meta bsp layer?

[S . Jaritz]

Hej

I want to create an own meta-bsp package for my custom mainboard based on 
an ATMEL SAMA5D35 SoC. For that I checked the documentation 
http://www.yoctoproject.org/docs/2.2/bsp-guide/bsp-guide.html#using-the-yocto-projects-bsp-tools
.

For me it is not clear how to create a bsp package based on the meta-atmel 
package. My goal is:

1.) use the SAMA5D35 SoC -> MACHINE ??= "sama5d3xek"
2.) append the device tree by adding: "mySAMA.dts" and "mySAMAmb.dtsi" 
(they use the dts files like #include "sama5d3.dtsi" from meta-atmel)
3.) adding my own defconfig for the kernel build
4.) change the configuration "at91bootstrap" which comes with the 
meta-atmel
5.) add some own SW packages

I created a working meta-mySAMA layer. It has grown over the time into 
some kind of meta-bsp. Think it would be nice to round everthing up by 
creating an own meta-bsp - to make it beautiful.

Is there a tutorial for that? Or can someone explan the steps form using 
"yocto-bsp create mySAMA "?

Regads!

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] What is the common way to extend an package without bbappend?

[S . Jaritz]

Hej

I want to install apache2 + a website. For that I need to copy my website 
to the std. dir defined in the apache config file. In my thinking my 
website uses the apache service to be aviable and therefore is an own 
package (myweb.bb). This package contains the dependency to the "apache2" 
recipe.

When populate_sysroot is called in myweb.bb finishes with the error:

myweb-1.0-r0 do_populate_sysroot: The recipe myweb is trying to install 
files into a shared area when those files already exist. Those files and 
their manifest location are:
 
/home/user/myTC/poky/build/tmp/sysroots/sama5d3xek/usr/share/apache2/htdocs/index.html

because the index.html needs to be overwritten.

Is there a easy way to overwrite or tell bitbake to uses my index.html?

regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: "bitbake virtual/kernel -c menuconfig" seems to be broken

[S . Jaritz]

When I run 'bitbake core-image-minimal' before it works. Think Roberts 
work arround points at the right spot(because the populate sysroot is 
called through core-image-minimal build). Maybe add this trick to the 
documentation.

Stefan

ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"robert.berger@gmane" 
An: yocto@yoctoproject.org
Datum:  27.09.2016 12:50
Betreff:Re: [yocto] "bitbake virtual/kernel -c menuconfig" seems 
to be   broken
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

On 2016-09-27 11:03, s.jar...@esa-grimma.de wrote:
> Hej
>
> Some error occurred. I give a print (sorry for that German text - but
> the error should be clear):
> ##
>   GEN ./Makefile
>   HOSTLD  scripts/kconfig/mconf
> scripts/kconfig/mconf.o: In Funktion `show_help':
> mconf.c:(.text+0x914): Nicht definierter Verweis auf `stdscr'
> scripts/kconfig/lxdialog/checklist.o: In Funktion `print_arrows':

Did you try something like this [1] (I know it is strange)

bitbake ncurses -c populate_sysroot -f

[1] 
http://lists.openembedded.org/pipermail/openembedded-core/2015-May/105374.html


You might want to post those kind of bugs to bugzilla[2]

[2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7609


Regards,

Robert

-- 
___
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] "bitbake virtual/kernel -c menuconfig" seems to be broken

[S . Jaritz]

Hej

Some error occurred. I give a print (sorry for that German text - but the 
error should be clear):
##
  GEN ./Makefile
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf.o: In Funktion `show_help':
mconf.c:(.text+0x914): Nicht definierter Verweis auf `stdscr'
scripts/kconfig/lxdialog/checklist.o: In Funktion `print_arrows':
checklist.c:(.text+0x2c): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x4c): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x54): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x66): Nicht definierter Verweis auf `waddnstr'
checklist.c:(.text+0x76): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x9f): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0xa7): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0xe3): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0xeb): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0xf2): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0xfa): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x101): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x109): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x110): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x143): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x14b): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x152): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x15a): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x161): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x169): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x170): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x178): Nicht definierter Verweis auf `waddch'
scripts/kconfig/lxdialog/checklist.o: In Funktion `print_item':
checklist.c:(.text+0x201): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x224): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x23d): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x288): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x2ae): Nicht definierter Verweis auf `waddnstr'
checklist.c:(.text+0x2c7): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x2cf): Nicht definierter Verweis auf `wrefresh'
checklist.c:(.text+0x321): Nicht definierter Verweis auf `wprintw'
checklist.c:(.text+0x34f): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x361): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x388): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x3a6): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x3c8): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x3dd): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x3f3): Nicht definierter Verweis auf `wmove'
scripts/kconfig/lxdialog/checklist.o: In Funktion `print_buttons':
checklist.c:(.text+0x481): Nicht definierter Verweis auf `wmove'
scripts/kconfig/lxdialog/checklist.o: In Funktion `dialog_checklist':
checklist.c:(.text+0x5a5): Nicht definierter Verweis auf `stdscr'
checklist.c:(.text+0x5ee): Nicht definierter Verweis auf `stdscr'
checklist.c:(.text+0x646): Nicht definierter Verweis auf `newwin'
checklist.c:(.text+0x65b): Nicht definierter Verweis auf `keypad'
checklist.c:(.text+0x6a3): Nicht definierter Verweis auf `wmove'
checklist.c:(.text+0x6af): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x6b7): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x6db): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x6e7): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x70f): Nicht definierter Verweis auf `acs_map'
checklist.c:(.text+0x717): Nicht definierter Verweis auf `waddch'
checklist.c:(.text+0x77d): Nicht definierter Verweis auf `subwin'
checklist.c:(.text+0x78f): Nicht definierter Verweis auf `keypad'
checklist.c:(.text+0x923): Nicht definierter Verweis auf `wnoutrefresh'
checklist.c:(.text+0x92d): Nicht definierter Verweis auf `wnoutrefresh'
checklist.c:(.text+0x932): Nicht definierter Verweis auf `doupdate'
checklist.c:(.text+0x94e): Nicht definierter Verweis auf `wgetch'
checklist.c:(.text+0xa6d): Nicht definierter Verweis auf `wnoutrefresh'
checklist.c:(.text+0xa75): Nicht definierter Verweis auf `wrefresh'
checklist.c:(.text+0xa8e): Nicht definierter Verweis auf `delwin'
checklist.c:(.text+0xa98): Nicht definierter Verweis auf `delwin'
checklist.c:(.text+0xb3d): Nicht definierter Verweis auf `delwin'
checklist.c:(.text+0xb47): Nicht definierter Verweis auf `delwin'
checklist.c:(.text+0xb53): Nicht definierter Verweis auf `stdscr'
checklist.c:(.text+0xbbe): Nicht definierter Verweis auf `scrollok'
checklist.c:(.text+0xbcb): Nicht definierter Verweis auf `wscrl'
checklist.c:(.text+0xbd5): Nicht definierter Verweis auf `scrollok'
checklist.c:(.text+0xc30): Nicht definierter Verweis auf `wnoutrefresh'
checklist.c:(.text+0xc38): Nicht definierter Verweis auf `wrefresh'

[yocto] Antwort: Re: How to extract an archive in a git repostry and copy it to a defined position in the rootfs? (Solved)

[S . Jaritz]

Thanks for the help! The solution is simple. As mentioned by Ross No 
do_fetch extension is needed. The extract + copy goes into do_install.

 part of the recipe 
do_install () {
install -d ${D}/opt
tar -xzf example.tar.gz -C ${D}/opt/
}

FILES_${PN} += "/opt/*"


Regards

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Burton, Ross" 
An: s.jar...@esa-grimma.de
Kopie:  Yocto Project 
Datum:  13.09.2016 11:59
Betreff:Re: [yocto] How to extract an archive in a git repostry 
and copy it to a defined position in the rootfs?




On 13 September 2016 at 08:08,  wrote:
??? do_fetch_append () { 
???extract ${S}/example.tar.gz 
??? }  

??? do_install () { 
???copy ${S}/ ${D}/opt/ 
??? } 

It's a tarball so use "tar" to extract, and you'll need to mkdir ${D}/opt 
before copying. but that's barely just pseudocode.

The only gotcha is that do_fetch() is a Python function so you can't just 
append shell code.  Simply move the extract into do_install().

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

[yocto] How to extract an archive in a git repostry and copy it to a defined position in the rootfs?

[S . Jaritz]

Hej

I like to build an package out of a git repro. This git repro contains 
compressed files. One of these files I like to copy into my package. I 
looked into the documentation, but it is only described how to use the 
fetcher of bitbake. Think I need to add some extra lines of instruction 
after fetching.

Maybe you have an idea how to solve that.

My example:
#Source:
-> gitsm:/myGitServer.com/UnpackExample;protocol=http;branch=master
-> Dir struct:
- UnpackExample
- win
- linux
- x86
- arm
- example.tar.gz
#Dest:
example.tar.gz -> opt/*.*
del opt/xyz.bin

#Pseudo recipe:
SUMMARY = "my test"
SECTION = "test"
LICENSE = "CLOSED"

PVBASE := "${PV}"
PV = "${PVBASE}.${SRCPV}"

SRCREV = "${AUTOREV}"
SRC_URI = 
"gitsm:/myGitServer.com/UnpackExample;protocol=http;branch=master"

S = "${WORKDIR}/git/linux/arm"

??? do_fetch_append () {
??? extract ${S}/example.tar.gz
??? }


??? do_install () {
??? copy ${S}/ ${D}/opt/
??? }

FILES_${PN} += "/opt/*"

# skip QA that is checking for the GNU_HASH
INSANE_SKIP_${PN} += "ldflags"
## end of recipe 

Regards!

Stefan

ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to add a textline to the busybox-syslog syslog.conf?

[S . Jaritz]

Hej ho

I have an app that is using syslog. For it I like to set the amount of log 
data.

I am using the std. yocto(krogoth) together with the std. meta-atmel 
layer. This layers are installing the "busybox-syslog"-package. This comes 
with the "/etc/syslog.conf" file.

My question is: How to append the syslog.conf with a line like 
"myApp,auth.notice /var/log/messages" out of a recipe?

My idea of the dummy recipe looks like:
 myApp.bb 
SUMMARY = "myApp"
SECTION = "demo"
LICENSE = "GPL"

inherit cmake

DEPENDS = "busybox-syslog"

SRC_URI = "gitsm://mygit/myApp.git;protocol=http;branch=develop"

PV = "1.0.0"

S = "${WORKDIR}/git/"

BBCLASSEXTEND = "native nativesdk"

do_install_append() {
echo 'myApp.*   /var/log/messages' >> /etc/syslog.conf
}
#

Any ideas how to do it in a nice way?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to generate a debug version of a single application and deploy it into the image?

[S . Jaritz]

Hej

Some software can be only tested on the final system. For that it would be 
usefull to start with a debug version of that app and change it later to 
release.

In my case I have a software which do logging. The amount of the logs 
depends on type of the build (Release skips all debug messages). Let's 
assume that my recipe for the software(myApp) is called myApp.bb. It is 
downloaded from an external git source and build through cmake.

Some idea how to do that?

Below the pseudo recipe as a starting point:
### myApp.bb ###
SUMMARY = "my App"
SECTION = "my"
LICENSE = "CLOSED"

inherit cmake

DEPENDS = "libconfig libg3log"

SRCREV = "${AUTOREV}"
SRC_URI = "gitsm://myGitSrv/myApp;protocol=http;branch=develop"

PVBASE := "${PV}"
PV = "${PVBASE}.${SRCPV}"

S = "${WORKDIR}/git/"

BBCLASSEXTEND = "native nativesdk"


Regads!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] if else blocks in recipes(bitbake)

[S . Jaritz]

Hej

If have a simple problem. On one system a program is started as a daemon 
and on the other one not. In my recipe the program is build. by using 
update-rc.d I create the init script for systemV. The code looks like:
##
SUMMARY = "myApp"
SECTION = "myApp"
LICENSE = "CLOSED"

DEPENDS = "dbus glibmm libsigc++-2.0 libconfig"
RDEPENDS_${PN} = "bash initscripts"

inherit cmake update-rc.d

SRCREV = "${AUTOREV}"
SRC_URI = "gitsm://myServer/myApp;protocol=http;branch=develop"

PVBASE := "${PV}"
PV = "${PVBASE}.${SRCPV}"

S = "${WORKDIR}/git/"

INITSCRIPT_PARAMS = "start 95 2 3 4 5 . stop 01 0 1 6 ."
INITSCRIPT_NAME = "myAppD.sh"

CONFFILES_${PN} += "${sysconfdir}/init.d/myAppD.sh"
##
Would like to that(pseudo-code):
##
BUILDVAR = "yes"

if BUILDVAR == "yes" then
INITSCRIPT_PARAMS = "start 95 2 3 4 5 . stop 01 0 1 6 ."
INITSCRIPT_NAME = "myAppD.sh"
 
CONFFILES_${PN} += "${sysconfdir}/init.d/myAppD.sh"
endif
##

How to tell this bitbake? 

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [fixed] Antwort: Re: Antwort: Re: How to set the sysroot toolchain to hard float

[S . Jaritz]

The problem was fixed. Updating meta-atmel to the current version fixes 
the dpkg error by appending the architecture parameter to the dkpg recipe 
(
https://github.com/linux4sam/meta-atmel/commit/63d4287f50b89496a4c72e3b5845e59c55887451
).

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"robert.berger@gmane" 
An: yocto@yoctoproject.org
Kopie:  public-yocto-EtnWKYl6rD/WsZ/bQMPhNw 
, Khem Raj 

Datum:  06.08.2016 09:23
Betreff:Re: [yocto] Antwort: Re: How to set the sysroot toolchain 
to hard float
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

On 2016-08-05 10:24, s.jar...@esa-grimma.de wrote:
>
> @TOOLCHAIN_OPTIONS: Where these are set in custom layers(like 
meta-atmel)?
>

If you ask me I would say here [1]:

DEFAULTTUNE = "cortexa5thf"

Here [2] are the available HF options:

# HF Tunes
AVAILTUNES += "cortexa5hf cortexa5thf cortexa5hf-neon cortexa5thf-neon"

[1] 
https://github.com/linux4sam/meta-atmel/blob/master/conf/machine/include/sama5d3.inc

[2] 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine/include/tune-cortexa5.inc


Regards,

Robert


-- 
___
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] Antwort: Re: Antwort: Re: How to set the sysroot toolchain to hard float

[S . Jaritz]

Hej ho

Thank you. I already know the files. My question was targeting the way how 
to set the tune option manually.

Maybee something is missed up by the layers. My bblayers.conf looks like:
#
# POKY_BBLAYERS_CONF_VERSION is increased each time 
build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
myTC/poky/meta \
myTC/poky/meta-poky \
myTC/poky/meta-yocto-bsp \
myTC/poky/meta-atmel \
myTC/poky/meta-skeleton \
myTC/poky/meta-openembedded/meta-oe \
myTC/poky/meta-openembedded/meta-networking \
myTC/poky/meta-openembedded/meta-python \
myTC/poky/meta-mylayer \
"
#

The priorities are set that way:

BBFILE_PRIORITY_atmel = "10"
BBFILE_PRIORITY_mylayer = "20"

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"robert.berger@gmane" 
An: yocto@yoctoproject.org
Kopie:  public-yocto-EtnWKYl6rD/WsZ/bQMPhNw 
, Khem Raj 

Datum:  06.08.2016 09:23
Betreff:Re: [yocto] Antwort: Re: How to set the sysroot toolchain 
to hard float
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

On 2016-08-05 10:24, s.jar...@esa-grimma.de wrote:
>
> @TOOLCHAIN_OPTIONS: Where these are set in custom layers(like 
meta-atmel)?
>

If you ask me I would say here [1]:

DEFAULTTUNE = "cortexa5thf"

Here [2] are the available HF options:

# HF Tunes
AVAILTUNES += "cortexa5hf cortexa5thf cortexa5hf-neon cortexa5thf-neon"

[1] 
https://github.com/linux4sam/meta-atmel/blob/master/conf/machine/include/sama5d3.inc

[2] 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine/include/tune-cortexa5.inc


Regards,

Robert


-- 
___
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] Antwort: Re: Antwort: Re: Antwort: Re: How to set the sysroot toolchain to hard float

[S . Jaritz]

when forcing dpkg it is installed and it works.

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Khem Raj 
An: s.jar...@esa-grimma.de
Kopie:  Yocto Project 
Datum:  05.08.2016 10:00
Betreff:Re: Antwort: Re: Antwort: Re: [yocto] How to set the 
sysroot toolchain to hard float





On 8/5/16 12:52 AM, s.jar...@esa-grimma.de wrote:
> I read the printings like you and I am confused.
> let's take valgrind as example:
> 1.) the rootfs build goes to:
> 
/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/valgrind/3.11.0-r0/deploy-debs/cortexa5hf-vfp/valgrind_3.11.0-r0_armhf.deb
> 
> 
> the extension of the deb package say it its hard float.
> 
> 2.) I transfer it to my device
> 
> 3.) console at the evalboard
> #
> root@sama5d3xek:/tmp# dpkg -r valgrind
> (Reading database ... 14780 files and directories currently installed.)
> Removing valgrind:armhf (3.11.0-r0) ...
> root@sama5d3xek:/tmp# dpkg -i valgrind_3.11.0-r0_armhf.deb
> dpkg: error processing archive valgrind_3.11.0-r0_armhf.deb (--install):
>  package architecture (armhf) does not match system (armel)

can you force it using dpkg -i --force-architecture and see if the
installed package works ? if it does then its the dpkg package arches
which aren't correct.

> Errors were encountered while processing:
>  valgrind_3.11.0-r0_armhf.deb
> root@sama5d3xek:/tmp#
> #
> 
> I got the information from here(hope it works):
> 
https://books.google.de/books?id=yNi6BwAAQBAJ=PA148=PA148=yocto+set+floating+point=bl=HXh65nWpHc=4UElzv4dz70xECsqw5lnCYuUZiI=de=X=0ahUKEwjOhrib2KnOAhVB1RQKHbXkAPAQ6AEIQDAE#v=onepage=yocto%20set%20floating%20point=false

> 
> 
> Maybe the deb generation has a bug?
> 
> 
> Stefan Jaritz
> 
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
> 
> 
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
> 
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
> 
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
> 
> This e-mail may contain confidential and/or privileged information. If
> you are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> 
> 
> 
> Von:Khem Raj 
> An:s.jar...@esa-grimma.de
> Kopie:Yocto Project 
> Datum:05.08.2016 09:27
> Betreff:Re: Antwort: Re: [yocto] How to set the sysroot
> toolchain to hard float
> 
> 
> 
> 
> 
> 
> On 8/5/16 12:24 AM, s.jar...@esa-grimma.de wrote:
>> hej
>>
>> @find out:
>> transfer a build package into the evalboard and try to install it. I am
>> using deb packages. dpkg gives me an error  because of architecture.
>>
>> @print configuration output:
>> ###
>> Build Configuration:
>> BB_VERSION= "1.30.0"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING   = "universal"
>> TARGET_SYS= "arm-poky-linux-gnueabi"
>> MACHINE   = "sama5d3xek"
>> DISTRO= "poky-atmel"
>> DISTRO_VERSION= "2.1.1"
>> TUNE_FEATURES = "arm armv7a vfp thumb callconvention-hard
> 
> here it is marking that your build is using hard-float. are you running
> image 

[yocto] Antwort: Re: Antwort: Re: How to set the sysroot toolchain to hard float

[S . Jaritz]

I read the printings like you and I am confused.
let's take valgrind as example:
1.) the rootfs build goes to:
/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/valgrind/3.11.0-r0/deploy-debs/cortexa5hf-vfp/valgrind_3.11.0-r0_armhf.deb

the extension of the deb package say it its hard float.

2.) I transfer it to my device

3.) console at the evalboard
#
root@sama5d3xek:/tmp# dpkg -r valgrind
(Reading database ... 14780 files and directories currently installed.)
Removing valgrind:armhf (3.11.0-r0) ...
root@sama5d3xek:/tmp# dpkg -i valgrind_3.11.0-r0_armhf.deb
dpkg: error processing archive valgrind_3.11.0-r0_armhf.deb (--install):
 package architecture (armhf) does not match system (armel)
Errors were encountered while processing:
 valgrind_3.11.0-r0_armhf.deb
root@sama5d3xek:/tmp#
#

I got the information from here(hope it works):
https://books.google.de/books?id=yNi6BwAAQBAJ=PA148=PA148=yocto+set+floating+point=bl=HXh65nWpHc=4UElzv4dz70xECsqw5lnCYuUZiI=de=X=0ahUKEwjOhrib2KnOAhVB1RQKHbXkAPAQ6AEIQDAE#v=onepage=yocto%20set%20floating%20point=false

Maybe the deb generation has a bug?


Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Khem Raj 
An: s.jar...@esa-grimma.de
Kopie:  Yocto Project 
Datum:  05.08.2016 09:27
Betreff:Re: Antwort: Re: [yocto] How to set the sysroot toolchain 
to hard float





On 8/5/16 12:24 AM, s.jar...@esa-grimma.de wrote:
> hej
> 
> @find out:
> transfer a build package into the evalboard and try to install it. I am
> using deb packages. dpkg gives me an error  because of architecture.
> 
> @print configuration output:
> ###
> Build Configuration:
> BB_VERSION= "1.30.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "sama5d3xek"
> DISTRO= "poky-atmel"
> DISTRO_VERSION= "2.1.1"
> TUNE_FEATURES = "arm armv7a vfp thumbcallconvention-hard

here it is marking that your build is using hard-float. are you running
image from same build on the target ? or is it some prebuilt image that
you are trying to add on to ?

>cortexa5"
> TARGET_FPU= "hard"
> meta 
> meta-poky 
> meta-yocto-bsp= "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab"
> meta-atmel= "krogoth:784a6a7fe94e6939325f60f4dd2cc24987ff090d"
> meta-skeleton = "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab"
> meta-oe 
> meta-networking 
> meta-python   = "krogoth:247b1267bbe95719cd4877d2d3cfbaf2a2f4865a"
> ###
> 
> @TOOLCHAIN_OPTIONS: Where these are set in custom layers(like 
meta-atmel)?
> 
> regards
> 
> Stefan Jaritz
> 
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
> 
> 
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
> 
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
> 
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
> 
> This e-mail may contain confidential and/or privileged information. If
> you are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> 
> 
> 
> Von:Khem Raj 
> An:s.jar...@esa-grimma.de, Yocto Project 

[yocto] Antwort: Re: How to set the sysroot toolchain to hard float

[S . Jaritz]

hej

@find out:
transfer a build package into the evalboard and try to install it. I am 
using deb packages. dpkg gives me an error  because of architecture.

@print configuration output:
###
Build Configuration:
BB_VERSION= "1.30.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "sama5d3xek"
DISTRO= "poky-atmel"
DISTRO_VERSION= "2.1.1"
TUNE_FEATURES = "arm armv7a vfp thumbcallconvention-hard   
  cortexa5"
TARGET_FPU= "hard"
meta 
meta-poky 
meta-yocto-bsp= "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab"
meta-atmel= "krogoth:784a6a7fe94e6939325f60f4dd2cc24987ff090d"
meta-skeleton = "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab"
meta-oe 
meta-networking 
meta-python   = "krogoth:247b1267bbe95719cd4877d2d3cfbaf2a2f4865a"
###

@TOOLCHAIN_OPTIONS: Where these are set in custom layers(like meta-atmel)?

regards

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Khem Raj 
An: s.jar...@esa-grimma.de, Yocto Project 
Datum:  05.08.2016 09:16
Betreff:Re: [yocto] How to set the sysroot toolchain to hard float





On 8/5/16 12:04 AM, s.jar...@esa-grimma.de wrote:
> Hej
> 
> I am building for the Atmel Evalbaord SAMA5D3x a Yocto Image. It works
> fine, but sysroot toolchain is set to soft float instead of hard float.
> How can I set the sysroot toolchain to hard float?
> 
> My actual configuration:
> 1.) use meta-atmel layer
> 2.) in /build/conf/layer.conf -> MACHINE ??= "sama5d3xek"
> 
> @meta-atmel:
> /conf/machine/sama5d3xek.conf includes sama5d3.inc
> in this file:
> SOC_FAMILY = "sama5:sama5d3"
> DEFAULTTUNE = "cortexa5thf"
> 
> I am not understanding why for the sysroot the default tune is not used.
> Any ideas are welcome.

How did you find that out ? can you send your build configuration output
that bitbake prints when starting the build ?
secondly, TOOLCHAIN_OPTIONS is what decides this ABI
so when you use CC and CXX and friends, the right thing happens since it
will be appending TOOLCHAIN_OPTIONS to these vars. but if you use bare
cross compiler that will default to soft-float

> 
> 
> Regards!
> 
> Stefan Jaritz
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
> 
> 
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
> 
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
> 
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
> 
> This e-mail may contain confidential and/or privileged information. If
> you are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> 
> 

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

[yocto] How to set the sysroot toolchain to hard float

[S . Jaritz]

Hej

I am building for the Atmel Evalbaord SAMA5D3x a Yocto Image. It works 
fine, but sysroot toolchain is set to soft float instead of hard float. 
How can I set the sysroot toolchain to hard float?

My actual configuration:
1.) use meta-atmel layer
2.) in /build/conf/layer.conf -> MACHINE ??= "sama5d3xek"

@meta-atmel:
/conf/machine/sama5d3xek.conf includes sama5d3.inc
in this file:
SOC_FAMILY = "sama5:sama5d3"
DEFAULTTUNE = "cortexa5thf"

I am not understanding why for the sysroot the default tune is not used. 
Any ideas are welcome.


Regards!

Stefan Jaritz

ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] problem with package architecture

[S . Jaritz]

Hej

I am using the actual Yocto version. A Yocto Linux I is build based on the 
meta-atmel layer. The system seems to be "armel" but the packages are for 
"armhf". When running bitbake it shows:
##
Build Configuration:
BB_VERSION= "1.30.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "sama5d3xek"
DISTRO= "poky-atmel"
DISTRO_VERSION= "2.1.1"
TUNE_FEATURES = "arm armv7a vfp thumbcallconvention-hard   
  cortexa5"
TARGET_FPU= "hard"
meta 
meta-poky 
meta-yocto-bsp= "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab"
meta-atmel= "krogoth:784a6a7fe94e6939325f60f4dd2cc24987ff090d"
meta-skeleton = "krogoth:f5da2a5913319ad6ac2141438ba1aa17576326ab"
meta-oe 
meta-networking 
meta-python   = "krogoth:247b1267bbe95719cd4877d2d3cfbaf2a2f4865a"
##
When entering: dpkg -i mylib1_1.0.0+47f1cc5ce1-r0_armhf.deb
I got:
##
dpkg: error processing archive mylib1_1.0.0+47f1cc5ce1-r0_armhf.deb 
(--install):
 package architecture (armhf) does not match system (armel)
Errors were encountered while processing:
mylib1_1.0.0+47f1cc5ce1-r0_armhf.deb
##

For me it seems that the architecture is not rightfully set. I have no 
idea how to fix this problem. Any ideas for that?

I am patching the kernel by inserting an own devicetree file and kernel 
config in my own meta-layer. Maybee I got problems because of that?:
@meta-atmel->layer.conf 
BBFILE_PRIORITY_atmel = "10"
@meta_mylayer
BBFILE_PRIORITY_mylayer = "6"

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to set the console color by default

[S . Jaritz]

Hej

It is Friday and the week is almost over - it is time for some image 
beautifications!

Is there a switch to activate the console colours by default? If not - 
what is the preferred way to produce a nice coloured console?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Problems finding python when using a cmake recipe

[S . Jaritz]

It works fine! Problem solved

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Burton, Ross" 
An: s.jar...@esa-grimma.de
Kopie:  "yocto@yoctoproject.org" 
Datum:  14.07.2016 13:05
Betreff:Re: [yocto] Problems finding python when using a cmake 
recipe




On 14 July 2016 at 11:22,  wrote:
I want to create a recipe for an application. This application is 
generated through cmake. In the cmake file "CMakeLists.txt" is the 
passage: 
## 
include(FindPythonInterp) 
include(FindPythonLibs) 
 
add_custom_command(OUTPUT "${CMAKE_BINARY_DIR}/error.cpp" 
"${CMAKE_BINARY_DIR}/error.hpp"non_existant_file 
COMMENT "create error.cpp" 
COMMAND ${PYTHON_EXECUTABLE} "${CMAKE_SOURCE_DIR}/mc2cpp.py" 
"${CMAKE_SOURCE_DIR}/Common/ErrorCodes/Error_Build/Errors.mc" 
"${CMAKE_BINARY_DIR}/error" 
) 
## 

This generates a header and a cpp file, which contains some error codes. 
When executing the cmake in my common environment it works fine. Under 
Bitbake it fails. Python is not found. 

This is because the cmake class stops cmake from finding binaries on the 
host.  I'm not convinced this is the right thing to do but haven't had the 
time to research the problem.

Add OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM = "BOTH" to your recipe after 
inherit cmake and it will look for and find the Python interpretter in 
/usr/bin.

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

[yocto] Problems finding python when using a cmake recipe

[S . Jaritz]

Hej

I want to create a recipe for an application. This application is 
generated through cmake. In the cmake file "CMakeLists.txt" is the 
passage:
##
include(FindPythonInterp)
include(FindPythonLibs)

add_custom_command(OUTPUT "${CMAKE_BINARY_DIR}/error.cpp" 
"${CMAKE_BINARY_DIR}/error.hpp"non_existant_file
COMMENT "create error.cpp"
COMMAND ${PYTHON_EXECUTABLE} "${CMAKE_SOURCE_DIR}/mc2cpp.py" 
"${CMAKE_SOURCE_DIR}/Common/ErrorCodes/Error_Build/Errors.mc" 
"${CMAKE_BINARY_DIR}/error"
)
##

This generates a header and a cpp file, which contains some error codes. 
When executing the cmake in my common environment it works fine. Under 
Bitbake it fails. Python is not found.

How to configure the recipe or the configuration to get it run?

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to install a service generated by update-rc.d?

[S . Jaritz]

Yes - The installation of the can_if into /etc/init.d was missing.

By adding:

do_install () {
install -d ${D}${sysconfdir}/init.d
cat ${WORKDIR}/can_if | \
  sed -e 's,/etc,${sysconfdir},g' \
  -e 's,/usr/sbin,${sbindir},g' \
  -e 's,/var,${localstatedir},g' \
  -e 's,/usr/bin,${bindir},g' \
  -e 's,/usr,${prefix},g' > ${D}${sysconfdir}/init.d/can_if
chmod a+x ${D}${sysconfdir}/init.d/can_if
}

It was solved!

Merci & Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Anders Darander 
An: yocto@yoctoproject.org
Datum:  06.07.2016 11:40
Betreff:Re: [yocto] How to install a service generated by 
update-rc.d?
Gesendet von:   yocto-boun...@yoctoproject.org



* s.jar...@esa-grimma.de  [160706 11:22]:
> I want to start a service that generates Sockets for the CAN Modules. 
> Manually configuring the system is no problem, but I like to have it 
done 
> by yocto. Below I give the code of my recipe (socketcan.bb):

> SUMMARY = "the config for the can socket interface"
> SECTION = "CAN"
> LICENSE = "CLOSED"

> inherit update-rc.d

> RDEPENDS_${PN} = "initscripts"

> DEPENDS = "iproute2"

> SRC_URI = "file://can_if"

> INITSCRIPT_PARAMS = "start 02 2 3 4 5 . stop 01 0 1 6 ."
> INITSCRIPT_NAME = "can_if"

> CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"

If this is the complete recipe, you never install can_if...

Cheers,
Anders

-- 
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
-- 
___
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] How to install 2 or more initscrips out form one recipe?

[S . Jaritz]

Hej

I run into a problem when I tried to install 3 initscrips out of one 
recipe. My recipe looks like:
#
SUMMARY = "demo cfg"
SECTION = "demo"
LICENSE = "CLOSED"

inherit update-rc.d

RDEPENDS_${PN} = "bash initscripts"

SRC_URI = "file://startA \
file://startB \
file://startC \
"

S = "${WORKDIR}"

do_install () {
install -d ${D}${sysconfdir}/
install -d ${D}${sysconfdir}/init.d/
install -m 0644 ${S}/startA ${D}${sysconfdir}/init.d/startA
install -m 0644 ${S}/startB ${D}${sysconfdir}/init.d/startB
install -m 0644 ${S}/startC ${D}${sysconfdir}/init.d/startC

chmod a+x ${D}${sysconfdir}/init.d/startA
chmod a+x ${D}${sysconfdir}/init.d/startB
chmod a+x ${D}${sysconfdir}/init.d/startC
}

INITSCRIPT_PACKAGES = "${PN} ${PN}_B ${PN}_C"
INITSCRIPT_NAME_${PN} = "startA"
INITSCRIPT_PARAMS_${PN} = "start 90 10"
INITSCRIPT_NAME_${PN}_B   = "startB"
INITSCRIPT_PARAMS_${PN}_B = "start 90 10"
INITSCRIPT_NAME_${PN}_C   = "startC"
INITSCRIPT_PARAMS_${PN}_C = "start 90 10"

CONFFILES_${PN} += "${sysconfdir}/init.d/startA"
CONFFILES_${PN} += "${sysconfdir}/init.d/startB"
CONFFILES_${PN} += "${sysconfdir}/init.d/startC"

FILES_${PN} += "${sysconfdir}/*"
#

The do_install works but initscript does not generates the link. I build 
that after this document 
http://docs.openembedded.ru/update-rc-d_class.html.

Any ideas?

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to set the prefix of a (cmake) recipe?

[S . Jaritz]

Hej

I want to install my software packages to the usr/local/bin dir. That is 
why I need to change the prefix form usr to usr/local. How to archive 
that?

The software is build through a cmake. Is there somethingt I need to think 
extra for setting the prefix?

Maybe I found some inconsistency:
@: GNU(
https://www.gnu.org/prep/standards/html_node/Directory-Variables.html)
the prefix should be "usr/local"
@ config for Bitbake:(
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf?h=blinky
)
the prefix is set to "usr"

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: How to create a directory for an SD-Card mount?

[S . Jaritz]

Problem solved! Thank you for the help.

It was solved by:

do_install () {
...
install -d ${D}/media/sd1
...
}

FILES_${PN} += "media/sd1"

@Mike:
I am using the meta-atmel. The mount dir is created. In my case I have a 
rule which mounts the sd card to mount/sd1, That's why I need to create 
sd1. But good idea, maybee I will change the rule, so it creates (if 
needed) the dir to mount.

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Mike Looijmans 
An: 
Datum:  07.07.2016 08:04
Betreff:Re: [yocto] How to create a directory for an SD-Card 
mount?
Gesendet von:   yocto-boun...@yoctoproject.org



On many embedded systems, /media/ is volatile. So you probably need to 
create 
an entry for a volatile dir.

Better is to create/delete the directory in the mount script. That also 
avoids 
races, since creating a directory is an atomic operation. And it allos you 
to 
mount multiple devices.

I'm actually surprised that this isn't already in place. Maybe you're 
missing 
some obscure udev package in your image?

On 06-07-16 20:09, Daniel. wrote:
> install -d ${D}/media/sd1
> ???
>
> 2016-07-06 11:44 GMT-03:00  :
>> Hej
>>
>> I managed to create and install a rule that should mount a sd card to
>> "/media/sd1".  To finish it, I need to create the directory "sd1" in 
media.
>> My recipe for the rule looks like:
>> ###
>> SUMMARY = "the udev rules for the board"
>> SECTION = "rules"
>> LICENSE = "CLOSED"
>>
>> SRC_URI = "file://50-mmc.rules \
>>  "
>> S = "${WORKDIR}"
>>
>> do_install () {
>>  install -d ${D}${sysconfdir}/udev/rules.d
>>  install -m 0644 ${WORKDIR}/50-mmc.rules
>> ${D}${sysconfdir}/udev/rules.d/
>> }
>> ###
>> How to create a dir in do_install which goes to the package?
>>
>> By the way:
>> I was also appending fstab after this article
>>
>> https://communities.intel.com/thread/49251
>>
>> Is there an better way to uncomment/modify that one line in fstab?
>>
>> Regards!
>>
>> Stefan Jaritz
>>
>> 
>> ESA Elektroschaltanlagen Grimma GmbH
>> Broner Ring 30
>> 04668 Grimma
>> Telefon: +49 3437 9211 176
>> Telefax: +49 3437 9211 26
>> E-Mail: s.jar...@esa-grimma.de
>> Internet: www.esa-grimma.de
>>
>>
>> Geschäftsführer:
>> Dipl.-Ing. Jörg Gaitzsch
>> Jörg Reinker
>>
>> Sitz der Gesellschaft: Grimma
>> Ust.-ID: DE 141784437
>> Amtsgericht: Leipzig, HRB 5159
>> Steuernummer: 238/108/00755
>>
>>
>> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
>> Informationen.
>> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
>> erhalten
>> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
>> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe 
dieser
>> Mail
>> ist nicht gestattet.
>>
>> This e-mail may contain confidential and/or privileged information. If 
you
>> are
>> not the intended recipient (or have received this e-mail in error) 
please
>> notify the sender immediately and destroy this e-mail. Any unauthorized
>> copying, disclosure or distribution of the material in this e-mail is
>> strictly
>> forbidden.
>> --
>> 
 
Kind regards,
 
Mike Looijmans
System Expert
 



TOPIC Products
 
 

Materiaalweg 4
 
 

5681 RJ Best
T:
+31 (0) 499 33 69 69

Postbus 440
E:
mike.looijm...@topicproducts.com

5680 AK Best
W:
www.topicproducts.com

The Netherlands




Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!

___
>> 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] How to create a directory for an SD-Card mount?

[S . Jaritz]

Hej

I managed to create and install a rule that should mount a sd card to 
"/media/sd1".  To finish it, I need to create the directory "sd1" in 
media.
My recipe for the rule looks like:
###
SUMMARY = "the udev rules for the board"
SECTION = "rules"
LICENSE = "CLOSED"

SRC_URI = "file://50-mmc.rules \
"
S = "${WORKDIR}"

do_install () {
install -d ${D}${sysconfdir}/udev/rules.d
install -m 0644 ${WORKDIR}/50-mmc.rules 
${D}${sysconfdir}/udev/rules.d/
}
###
How to create a dir in do_install which goes to the package?

By the way:
I was also appending fstab after this article

https://communities.intel.com/thread/49251

Is there an better way to uncomment/modify that one line in fstab?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to install a service generated by update-rc.d?

[S . Jaritz]

Hej,

I want to start a service that generates Sockets for the CAN Modules. 
Manually configuring the system is no problem, but I like to have it done 
by yocto. Below I give the code of my recipe (socketcan.bb):
#
SUMMARY = "the config for the can socket interface"
SECTION = "CAN"
LICENSE = "CLOSED"

inherit update-rc.d

RDEPENDS_${PN} = "initscripts"

DEPENDS = "iproute2"

SRC_URI = "file://can_if"

INITSCRIPT_PARAMS = "start 02 2 3 4 5 . stop 01 0 1 6 ."
INITSCRIPT_NAME = "can_if"

CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"
#
It has one file bash script "can_if". This contains the up and down 
commands. I want to generate at the /etc/rc*** Dirs the 
S02can_if/K01can_if links.
Building the recipe via "bitbake socketcan" works fine.
When generating the rootfs via "bitbake core-image-minimal" I got the 
following error:
#
ERROR: core-image-minimal-1.0-r0 do_rootfs: Unable to install packages. 
Command 
'/home/user/myTC/poky/build/tmp/sysroots/x86_64-linux/usr/bin/apt-get 
install --force-yes --allow-unauthenticated python-modules meteocontrol 
webmaint libg3logger0 packagegroup-core-ssh-openssh apt vim curl pmdb 
redis libcsv3 myuser boost packagegroup-core-boot libredox0 libemd2 
python-django python libev4 can-utils run-postinsts util-linux dpkg 
mymodules grep libhiredis0.13 libmydbus0 libconfig iproute2 p7zip 
socketcan' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
Package socketcan is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'socketcan' has no installation candidate

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/sama5d3xek-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.14597
ERROR: Task 9 
(/home/user/myTC/poky/meta/recipes-core/images/core-image-minimal.bb, 
do_rootfs) failed with exit code '1'
#

Any idea how to fix that?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] problem with installation pathes of recipes useing cmake + cpack

[S . Jaritz]

Hej

I have several recipes which are based on cmake.  At cmake is the "make 
package" enabled. It is based on CPack(debian).

I am using the predefined GNU installation dirs by 
"include(GNUInstallDirs)" and its variables like CMAKE_INSTALL_FULL_BINDIR 
etc.
(https://cmake.org/cmake/help/v3.0/module/GNUInstallDirs.html)

CMAKE_INSTALL_FULL_BINDIR is set to /usr/local/bin by default, when 
building the package on my development machine outside of Yocto. That is 
fine.

When building the same project in Yocto the CMAKE_INSTALL_FULL_BINDIR is 
set to usr/bin. Seems that the prefix is set by Yocto.

Any ideas how to fix that problem?

Regards

Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to re-set the libary path for the package manager/QA module

[S . Jaritz]

Hej

I want to build a library. It comes with a cmake based build. In these 
process the library is build and deployed together with 2 links. Like 
that:

libMyLib:
usr/lib/test/mylib.so
usr/lib/test/mylib.so.0
usr/lib/test/mylib.so.1.0.0

mylib.so and mylib.so.0 are links to mylib.so.1.0.0

The packing works fine but the QA tells: "
Files/directories were installed but not shipped in any package:
  /usr/lib/test/mylib.so.0
  /usr/lib/test/mylib.so.1.0.0
  /usr/lib/test/mylib.so
"

Any ideas how to set the

FILES_${PN} += "${libdir}/test/*.so.*"

in a right way?

Regards!

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: installation of kernel modules

[S . Jaritz]

Hej  Daniel,

Building the modules as rpm works fine but it fails for deb. The deb 
generation process seems a little buggy. I have discovered problems with 
naming recipes (the QA tries to find the license by a "lowercased" link).

I checked the package dir. It is fine. The 3 files (a.ko, b.ko, & c.ko) 
are placed rightfully. The splitting into packages produces 3 kernel 
module packages and the 6 standard packages(like dev, static, local, etc). 
I think the problem is that the module will be compiled and deployed 
together with the kernel and the common packages later at the do_rootfs. 
That's why the myKernelModules recipe is deployed at the tmp/wok/ 
dir (and not at the tmp/work/).

Regards,

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Daniel." 
An: s.jar...@esa-grimma.de
Kopie:  "yocto@yoctoproject.org" 
Datum:  21.06.2016 20:15
Betreff:Re: [yocto] installation of kernel modules



Take a look at deploy folder if your packages (rpm in my case) are
being created. I have faced problems where files go to -dev.rpm
packages and the yocto silently refuses to create empty .rpm package.

Regards,

2016-06-21 5:33 GMT-03:00  :
> Hej
>
> I have a problem when running do_rootfs() with some own kernel drivers
> included.
>
> My kernel recipe builds some easy GPIO drivers.
>
> # They come as one package:
> myKernelModules:
> -> a.ko
> -> b.ko
> -> c.ko
>
> # I build a recipe which creates:
> myKernelModules.bb
> -> packages-split/myKernelModules
> -> packages-split/kernel-module-a
> -> packages-split/kernel-module-b
> -> packages-split/kernel-module-c
> -> packages-split/myKernelModules-.
>
> # I try to pack/install my Module by adding to layer.conf:
>
> IMAGE_INSTALL_append=" myKernelModules"
>
> When I try to build the rootfs I got that error:
>
> The following packages have unmet dependencies:
>  myKernelModules : Depends: kernel-module-a but it is not installable
>Depends: kernel-module-b but it is not installable
>Depends: kernel-module-c but it is not installable
> E: Unable to correct problems, you have held broken packages.
>
> Any idea how to fix this problem?
>
> Regards!
>
> Stefan Jaritz
>
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If 
you
> are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Do or do not. There is no try"
  Yoda Master

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

[yocto] installation of kernel modules

[S . Jaritz]

Hej

I have a problem when running do_rootfs() with some own kernel drivers 
included.

My kernel recipe builds some easy GPIO drivers.

# They come as one package:
myKernelModules:
-> a.ko
-> b.ko
-> c.ko

# I build a recipe which creates:
myKernelModules.bb
-> packages-split/myKernelModules
-> packages-split/kernel-module-a
-> packages-split/kernel-module-b
-> packages-split/kernel-module-c
-> packages-split/myKernelModules-.

# I try to pack/install my Module by adding to layer.conf:
 
IMAGE_INSTALL_append=" myKernelModules" 

When I try to build the rootfs I got that error:

The following packages have unmet dependencies:
 myKernelModules : Depends: kernel-module-a but it is not installable
   Depends: kernel-module-b but it is not installable
   Depends: kernel-module-c but it is not installable
E: Unable to correct problems, you have held broken packages.

Any idea how to fix this problem?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Problems creating packages for kernel modules when switching from rpm to deb

[S . Jaritz]

Hej

I have encountered a problem, when I switched from rpm to deb. I have a 
recipe which generates 3 kernel modules. The compiling and packaging works 
fine. But when I do the do_rootfs it fails with:
##
ERROR: core-image-minimal-1.0-r0 do_rootfs: Unable to install packages. 
Command 
'/home/user/myTC/poky/build/tmp/sysroots/x86_64-linux/usr/bin/apt-get 
install --force-yes --allow-unauthenticated ..a lot printings ... returned 
100:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mymodules : Depends: kernel-module-mymoduleindi but it is not going to be 
installed
   Depends: kernel-module-mymodulecom but it is not going to 
be installed
   Depends: kernel-module-mymoduleled but it is not going to 
be installed
E: Unable to correct problems, you have held broken packages.

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/sama5d3xek-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.64715
ERROR: Task 9 
(/home/user/myTC/poky/meta/recipes-core/images/core-image-minimal.bb, 
do_rootfs) failed with exit code '1'
##

the recipe is called "mymodules.bb" in that I trigger a makefile which 
builds the 
mymodulesindi.ko
mymodulescom.ko
mymodulesled.ko
These are packed by the "inherit module" line.

Any idea how to solve that problem?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Found Error] Re: License problems when switching form RPM to DEB - looking for a easy way to fix it

[S . Jaritz]

Hej

I found the error at the QA check of the debian packages. The deb QA modul 
has problems resolving the links into the 
"sysroots//pkgdata/runtime-resolve". This is because there is a 
lowcase conversation of the recipe name:

p.e.:

"helloMyWorld.bb"

the name of the link is "helloMyWorld"

the QA module is searching for: "hellomyworld"

by renaming the recipe to lowcase letters solves the error. Maybe someone 
can fix it.

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.
- Weitergeleitet von Stefan Jaritz/User/ESA-Grimma/DE am 14.06.2016 
11:50 -

Von:Stefan Jaritz/User/ESA-Grimma/DE
An: "Burton, Ross" , 
roman.shaposhni...@globallogic.com
Kopie:  "yocto@yoctoproject.org" 
Datum:  13.06.2016 13:32
Betreff:Antwort: Re: [yocto] License problems when switching form 
RPM to DEB - looking for a easy way to fix it


Hej

I deleted the tmp and rebuild it. But the error stays. I added a licence 
file to the repro and added the

LICENSE="ESA"
LIC_FILES_CHKSUM="files://ESAlicense.txt;md5=.."

What's the connection between the LICENSE and LIC_FILES_CHKSUM field?
How the license manifest is build?

I think the error is releated to the point, that there is possibly no 
LICENSE entry connected to "ESA" or "CLOSED".
Below the error print:
##
ERROR: core-image-minimal-1.0-r0 do_rootfs: Error executing a python 
function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure 
was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:license_create_manifest(d)
 0003:
File: '/home/user/myTC/poky/meta/classes/license.bbclass', lineno: 48, 
function: license_create_manifest
 0044:pkg_dic = {}
 0045:for pkg in sorted(image_list_installed_packages(d)):
 0046:pkg_info = os.path.join(d.getVar('PKGDATA_DIR', True),
 0047:'runtime-reverse', pkg)
 *** 0048:pkg_name = os.path.basename(os.readlink(pkg_info))
 0049:
 0050:pkg_dic[pkg_name] = 
oe.packagedata.read_pkgdatafile(pkg_info)
 0051:if not "LICENSE" in pkg_dic[pkg_name].keys():
 0052:pkg_lic_name = "LICENSE_" + pkg_name
Exception: OSError: [Errno 2] No such file or directory: 
'/home/user/myTC/poky/build/tmp/sysroots/sama5d3xek/pkgdata/runtime-reverse/mycontrol'

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: 
license_create_manifest
ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/sama5d3xek-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.22140
ERROR: Task 9 
(/home/user/myTC/poky/meta/recipes-core/images/core-image-minimal.bb, 
do_rootfs) failed with exit code '1'
##

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Burton, Ross" 
An: 

[yocto] Antwort: Re: License problems when switching form RPM to DEB - looking for a easy way to fix it

[S . Jaritz]

Hej

I deleted the tmp and rebuild it. But the error stays. I added a licence 
file to the repro and added the

LICENSE="ESA"
LIC_FILES_CHKSUM="files://ESAlicense.txt;md5=.."

What's the connection between the LICENSE and LIC_FILES_CHKSUM field?
How the license manifest is build?

I think the error is releated to the point, that there is possibly no 
LICENSE entry connected to "ESA" or "CLOSED".
Below the error print:
##
ERROR: core-image-minimal-1.0-r0 do_rootfs: Error executing a python 
function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure 
was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:license_create_manifest(d)
 0003:
File: '/home/user/myTC/poky/meta/classes/license.bbclass', lineno: 48, 
function: license_create_manifest
 0044:pkg_dic = {}
 0045:for pkg in sorted(image_list_installed_packages(d)):
 0046:pkg_info = os.path.join(d.getVar('PKGDATA_DIR', True),
 0047:'runtime-reverse', pkg)
 *** 0048:pkg_name = os.path.basename(os.readlink(pkg_info))
 0049:
 0050:pkg_dic[pkg_name] = 
oe.packagedata.read_pkgdatafile(pkg_info)
 0051:if not "LICENSE" in pkg_dic[pkg_name].keys():
 0052:pkg_lic_name = "LICENSE_" + pkg_name
Exception: OSError: [Errno 2] No such file or directory: 
'/home/user/myTC/poky/build/tmp/sysroots/sama5d3xek/pkgdata/runtime-reverse/mycontrol'

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: 
license_create_manifest
ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/sama5d3xek-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.22140
ERROR: Task 9 
(/home/user/myTC/poky/meta/recipes-core/images/core-image-minimal.bb, 
do_rootfs) failed with exit code '1'
##

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Burton, Ross" 
An: s.jar...@esa-grimma.de
Kopie:  "yocto@yoctoproject.org" 
Datum:  09.06.2016 18:21
Betreff:Re: [yocto] License problems when switching form RPM to 
DEB - looking for a easy way to fix it




On 9 June 2016 at 15:52,  wrote:
I switched from RPM to DEB because the board configuration should be 
handled by a package manager. By doing so I ran into a QA problem. All the 
software provided by my colleagues I maked with 

Note that deb is the least-tested package manager, we generally recommend 
rpm or opkg over deb.  If you switched to deb because of the size of the 
tools on the target compared to rpm (as smart pulls in Python, it's not 
small) then you'll really like opkg.
 
LICENSE = "CLOSED" 

because they do not provide a license file. This works fine with the rpm 
generator, but when I use the debian generator - the QA from the 
"do_rootfs" fails with: 
[snip]

Very interesting, and I have seen this occasionally.  Does deleting your 
tmp/ and rebuilding from sstate solve this?

Ross

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

[yocto] Antwort: Re: Problems with do_rootfs when changing the user password

[S . Jaritz]

Hej

Thanks for the infos. I figured out that the common tutorial under 
meta-skeleton does not covers the change of the root password. Although 
"usermod -P" does not exits. Now the "usermod -p" wants a encrypted 
password. Looks like most of the examples at the www are little outdated. 
My question is now:

How are the steps to (re)set the root password?

If you like I would prefer to solve this question like a tutorial.

The starting point is a own layer ("myLayer") and a password 
("myNewPassword1234").

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Jussi Kukkonen 
An: s.jar...@esa-grimma.de
Kopie:  Yocto Project 
Datum:  09.06.2016 12:00
Betreff:Re: [yocto] Problems with do_rootfs when changing the user 
password



On 9 June 2016 at 12:00,  wrote:
>
> Hej
>
> I want to change the root password. For that I create the recipe 
"myNewPassword.bb" with:
> 
> SUMMARY = "my new password"
> SECTION = "new"
> LICENSE = "CLOSED"
>
> inherit extrausers
>
> EXTRA_USERS_PARAMS = "\
> usermod -P xyz root; \
> "
> 
>
> compiling and packaging works fine.
>
> In my layer I add at the layer.conf:
> 
> IMAGE_INSTALL_append=" myNewPassword"
> 
>
> When do_rootfs (core-image-minimal) the package could not be found. A 
deb(ug) Package was created.

If your package would contain no files, bitbake will not produce it at 
all. You should be able to override this with: 
ALLOW_EMPTY_${PN} = "1"

 - Jussi

 
>
> Regards!
>
> Stefan Jaritz
>
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If 
you are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is 
strictly
> forbidden.
> --
> ___
> 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] License problems when switching form RPM to DEB - looking for a easy way to fix it

[S . Jaritz]

Hej

I switched from RPM to DEB because the board configuration should be 
handled by a package manager. By doing so I ran into a QA problem. All the 
software provided by my colleagues I maked with 

LICENSE = "CLOSED"

because they do not provide a license file. This works fine with the rpm 
generator, but when I use the debian generator - the QA from the 
"do_rootfs" fails with:

ERROR: core-image-minimal-1.0-r0 do_rootfs: Error executing a python 
function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure 
was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:license_create_manifest(d)
 0003:
File: '/home/user/myTC/poky/meta/classes/license.bbclass', lineno: 48, 
function: license_create_manifest
 0044:pkg_dic = {}
 0045:for pkg in sorted(image_list_installed_packages(d)):
 0046:pkg_info = os.path.join(d.getVar('PKGDATA_DIR', True),
 0047:'runtime-reverse', pkg)
 *** 0048:pkg_name = os.path.basename(os.readlink(pkg_info))
 0049:
 0050:pkg_dic[pkg_name] = 
oe.packagedata.read_pkgdatafile(pkg_info)
 0051:if not "LICENSE" in pkg_dic[pkg_name].keys():
 0052:pkg_lic_name = "LICENSE_" + pkg_name
Exception: OSError: [Errno 2] No such file or directory: 
'/home/user/myTC/poky/build/tmp/sysroots/sama5d3xek/pkgdata/runtime-reverse/mycontrol'

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: 
license_create_manifest
ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/sama5d3xek-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.69642
ERROR: Task 9 
(/home/user/myTC/poky/meta/recipes-core/images/core-image-minimal.bb, 
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2383 tasks of which 2382 didn't need to be 
rerun and 1 failed.
No currently running tasks (2012 of 2388)


Is there a way to avoid that or do I have to provide for every recipe a 
license file?

I found a contribution about that: 
https://www.yoctoproject.org/blogs/khem/2014/suppliment-common-licenses-yocto-project

But ${LAYERDIR} seem not to be set. Maybe a small example can explain my 
problem in a good way. I have a layer with the following struct and 
modifications:

meta-myLayer
|- licenses
|-> myLicense
|- recipes-my
|-> myrecipe.bb

@meta-myLayer:
LICENSE_PATH += "${LAYERDIR}/licenses"

@myrecipe.bb
LICENSE = "myLicense"

Where is my error/what do I have to do for avoiding to add for every 
recipe a license file?

Regards!

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: Problems with do_rootfs when changing the user password

[S . Jaritz]

Thanks & done in that way

but the bitbake error "core-image-minimal-1.0-r0 do_rootfs: 
myNewPassword.bb not found in the base feeds" still remains

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Oleksandr Poznyak 
An: s.jar...@esa-grimma.de
Kopie:  yocto@yoctoproject.org
Datum:  09.06.2016 11:13
Betreff:Re: [yocto] Problems with do_rootfs when changing the user 
password



Hi,
Its better to change root passwd within ROOTFS_POSTPROCESS_COMMAND

Something like that:

set_root_passwd() {
.change passwd here
}

ROOTFS_POSTPROCESS_COMMAND += " set_root_passwd;"

Thanks,
Oleksandr Poznyak!

On Thu, Jun 9, 2016 at 12:00 PM,  wrote:
Hej 

I want to change the root password. For that I create the recipe 
"myNewPassword.bb" with: 
 
SUMMARY = "my new password" 
SECTION = "new" 
LICENSE = "CLOSED" 

inherit extrausers 

EXTRA_USERS_PARAMS = "\ 
usermod -P xyz root; \ 
" 
 

compiling and packaging works fine. 

In my layer I add at the layer.conf: 
 
IMAGE_INSTALL_append=" myNewPassword" 
 

When do_rootfs (core-image-minimal) the package could not be found. A 
deb(ug) Package was created. 

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.
--
___
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] Problems with do_rootfs when changing the user password

[S . Jaritz]

Hej

I want to change the root password. For that I create the recipe 
"myNewPassword.bb" with:

SUMMARY = "my new password"
SECTION = "new"
LICENSE = "CLOSED"

inherit extrausers

EXTRA_USERS_PARAMS = "\
usermod -P xyz root; \
"


compiling and packaging works fine.

In my layer I add at the layer.conf:

IMAGE_INSTALL_append=" myNewPassword"


When do_rootfs (core-image-minimal) the package could not be found. A 
deb(ug) Package was created.

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to execute a git submodule init/update?

[S . Jaritz]

Hej

I have a git source which need some submodules. For that I need to execute 
"git submodule init" and "git submodule update". Any idea how to do it in 
a comon way?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Solved] Antwort: Re: How to include a own libary into the toolchain(SDK) for an embeeded Linux generated by Yocto?

[S . Jaritz]

Hej

Problem solved! It worked like described by Rebert and on Stack Overflow.

Thanks for the help

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Robert Berger 
An: yocto@yoctoproject.org
Datum:  01.06.2016 09:15
Betreff:Re: [yocto] How to include a own libary into the 
toolchain(SDK) for an embeeded Linux generated by Yocto?
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

On 05/31/2016 06:03 PM, s.jar...@esa-grimma.de
wrote:> Hej,
>
> I am looking for an example where is shown how to include an own library
> into the toolchain.
>
> Let's call the library "myLib". For it I created an recipe "myLib.bb"
> and added:
>
> BBCLASSEXTEND = "native nativesdk"

Like this you can build a myLib-native (for your host - x86) version and
it should be added as an x86 library to your nativesdk.

see:

http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#var-BBCLASSEXTEND


>
> In my "local.conf" I added:
>
> IMAGE_INSTALL_append = " myLib"
>
> When building the SDK by:
>
> $ bitbake myTarget -c populate_sdk
>
> It produces a installer for the SDK and two manifest files. "myLib" is
> only included at the target manifest and not on the host. How can I
> include myLib on the host system?

Do you want myLib-native?

>
> The idea is, that a other person can build software on his system
> without the Yocto system. Only by using the toolchain he can generate
> binaries, which can be transferred and executed at the evalboard.

I guess you want something else. You want e.g. the ARM library myLib in
your sysroot plus maybe header files.

What happens if you create a recipe like a testcase for your library
which DEPENDS_append = " myLib" and then you IMAGE_INSTALL_append = "
myLib testmyLib", rebuild the image and populate_sdk?

>
>
> Regards!

Regards,

Robert

>
> PS: I put the question on stackoverflow:
>
http://stackoverflow.com/questions/37548851/how-to-include-a-own-libary-into-the-toolchainsdk-for-an-embeeded-linux-genera

>
>
>
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If
> you are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
>
>
> --
>

...To go faster, slow down. Everybody who knows about orbital mechanics
understands that.- Scott Cherf

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1


-- 
___
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] Antwort: Re: How to include a own libary into the toolchain(SDK) for an embeeded Linux generated by Yocto?

[S . Jaritz]

Thanks for the reply

Like you thought - I want to include the lib + headers.

I included the "myLib" via 

IMAGE_INSTALL_append = " myLib"

and have a project

IMAGE_INSTALL_append = " myProject"

which has in it's recipe

DEPENDS = "myLib"

In my eyes this should be enough.

When looking into the toolchain I found:

myLib.h
myLib.c

but not

libmyLib.so
libmyLib.so.0
libmyLib.so.0.0.0.0


Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Robert Berger 
An: yocto@yoctoproject.org
Datum:  01.06.2016 09:15
Betreff:Re: [yocto] How to include a own libary into the 
toolchain(SDK) for an embeeded Linux generated by Yocto?
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,

On 05/31/2016 06:03 PM, s.jar...@esa-grimma.de
wrote:> Hej,
>
> I am looking for an example where is shown how to include an own library
> into the toolchain.
>
> Let's call the library "myLib". For it I created an recipe "myLib.bb"
> and added:
>
> BBCLASSEXTEND = "native nativesdk"

Like this you can build a myLib-native (for your host - x86) version and
it should be added as an x86 library to your nativesdk.

see:

http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#var-BBCLASSEXTEND


>
> In my "local.conf" I added:
>
> IMAGE_INSTALL_append = " myLib"
>
> When building the SDK by:
>
> $ bitbake myTarget -c populate_sdk
>
> It produces a installer for the SDK and two manifest files. "myLib" is
> only included at the target manifest and not on the host. How can I
> include myLib on the host system?

Do you want myLib-native?

>
> The idea is, that a other person can build software on his system
> without the Yocto system. Only by using the toolchain he can generate
> binaries, which can be transferred and executed at the evalboard.

I guess you want something else. You want e.g. the ARM library myLib in
your sysroot plus maybe header files.

What happens if you create a recipe like a testcase for your library
which DEPENDS_append = " myLib" and then you IMAGE_INSTALL_append = "
myLib testmyLib", rebuild the image and populate_sdk?

>
>
> Regards!

Regards,

Robert

>
> PS: I put the question on stackoverflow:
>
http://stackoverflow.com/questions/37548851/how-to-include-a-own-libary-into-the-toolchainsdk-for-an-embeeded-linux-genera

>
>
>
> 
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jar...@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If
> you are
> not the intended recipient (or have received this e-mail in error) 
please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
>
>
> --
>

...To go faster, slow down. Everybody who knows about orbital mechanics
understands that.- Scott Cherf

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1


-- 
___
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] How to include a own libary into the toolchain(SDK) for an embeeded Linux generated by Yocto?

[S . Jaritz]

Hej,

I am looking for an example where is shown how to include an own library 
into the toolchain.

Let's call the library "myLib". For it I created an recipe "myLib.bb" and 
added:

BBCLASSEXTEND = "native nativesdk"

In my "local.conf" I added:

IMAGE_INSTALL_append = " myLib"

When building the SDK by:

$ bitbake myTarget -c populate_sdk

It produces a installer for the SDK and two manifest files. "myLib" is 
only included at the target manifest and not on the host. How can I 
include myLib on the host system?

The idea is, that a other person can build software on his system without 
the Yocto system. Only by using the toolchain he can generate binaries, 
which can be transferred and executed at the evalboard.


Regards!

PS: I put the question on stackoverflow: 
http://stackoverflow.com/questions/37548851/how-to-include-a-own-libary-into-the-toolchainsdk-for-an-embeeded-linux-genera



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to set a cmake cache variable to a spezific value?

[S . Jaritz]

Hej

I want to build a recipe for a cmake based application. To make it run I 
need to set a cached cmake variable.

What is the common/best way to achive it?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How can I set a recipe that its binaries become available at cross-compile time?

[S . Jaritz]

Hej

I a cmake based application, some code generation via dbusxx-xml2cpp. It 
is provided by the dbuss-c++ lib. A recipe can be found under:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/meta-ivi-demo/recipes-extended/dbus-c++?id=b90c2a20744e1e82b2169a88e68d7677bec907b6

It working and it's compiling & linking, "dbusxx-xml2cpp" is included at 
the native build.

How can I set a recipe that its binaries become available at cross-compile 
time?

Best regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to include packages for the cmake build process?

[S . Jaritz]

Hej

I have some general question. Actual I am try to build an older software. 
It is based on cmake. At the build process doxygen, python, sed, 
dbusxx-xml2cpp are called. They are included via the 
"findprogram"/"find_package" command.

How to include external programs like python, sed etc. in my build 
toolchain? Do I use DPENDS = " python"?

The weak points are in the Makefile.txt when:

find_package(PythonInterp REQUIRED)

As example I add a non working recipe for doxygen:

### doxygen_1.8.bb ###
DESCRIPTION = "Utilities for generating documentation from source code"
HOMEPAGE = "http://www.doxygen.org/;
SECTION = "console/utils"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://LICENSE;md5=b380c86cea229fa42b9e543fc491f5eb"

DEPENDS = "flex-native bison-native python-native"

inherit cmake

SRCREV = "a6d4f4df45febe588c38de37641513fd576b998f"
SRC_URI = "git://github.com/doxygen/doxygen.git"

S = "${WORKDIR}/git"

#EXTRA_OECONF = "--prefix ${prefix}"

BBCLASSEXTEND = "native"
#

Mit freundlichen Grüßen

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] autotools error when building libdbus-c++; autoreconf "possibly undefined macro: AC_DEFINE"

[S . Jaritz]

Hej

I try to build the libdbus-c++ libary. The build process is based on 
autotools. When compiling it  do_configure throws an error. The macro 
"AC_DEFINE" is not found. Any idea how to make autoreconf run?

Below I listed to recipe and after the Error plot

# libdbus-c++_0.9.bb ###
SUMMARY = "libdbus-c++"
SECTION = "ccc"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"

inherit autotools

SRC_URI[md5sum] = "e752116f523fa88ef041e63d3dee4de2"
SRC_URI[sha256sum] = 
"bc11ac297b3cb010be904c72789695543ee3fdf3d75cdc8225fd371385af4e61"
SRC_URI = "
https://sourceforge.net/projects/dbus-cplusplus/files/dbus-c++/0.9.0/libdbus-c++-0.9.0.tar.gz
"

S = "${WORKDIR}/libdbus-c++-0.9.0"

BBCLASSEXTEND += "native"


# Error ###
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal 
--system-acdir=/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/build/aclocal-copy/
 
-I 
/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/libdbus-c++-0.9.0/m4/
 
-I 
/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/libdbus-c++-0.9.0/m4/
 
--force -I m4
| autoreconf: configure.ac: tracing
| autoreconf: running: libtoolize --copy --force
| libtoolize: putting auxiliary files in '.'.
| libtoolize: copying file './ltmain.sh'
| libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
| libtoolize: copying file 'm4/libtool.m4'
| libtoolize: copying file 'm4/ltoptions.m4'
| libtoolize: copying file 'm4/ltsugar.m4'
| libtoolize: copying file 'm4/ltversion.m4'
| libtoolize: copying file 'm4/lt~obsolete.m4'
| autoreconf: running: 
/home/user/myTC/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf 
--include=/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/libdbus-c++/0.9-r0/libdbus-c++-0.9.0/m4/
 
--force
| configure.ac:54: error: possibly undefined macro: AC_DEFINE
|   If this token and others are legitimate, please use 
m4_pattern_allow.
|   See the Autoconf documentation.
| autoreconf: 
/home/user/myTC/poky/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf 
failed with exit status: 1


Mit freundlichen Grüßen

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Solved - Antwort: RE: how to install a kernel module

[S . Jaritz]

I solved that problem

Using 

IMAGE_INSTALL += "ledmodule"

instead of

IMAGE_INSTALL_append = " ledmodule"

caused that the module was installed.

I found the hint in

https://communities.intel.com/thread/56810?start=0=0

Thanks for the help. Maybe a tip in the recipe template "hello_mod" could 
help other people trying to build theire own modules.

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:Stefan Jaritz/User/ESA-Grimma/DE
An: "Esponde, Joel" , Christian Ege 

Kopie:  "yocto@yoctoproject.org" 
Datum:  13.05.2016 11:53
Betreff:Antwort: RE: [yocto] how to install a kernel module


Thanks for taking the time to help me

I tried your approach but it does not worked.

I tell what I figured out so far:

I.) checking the target system
1.) When flashing the images into my device and boot the system, the 
driver is not loaded.
2.) lsmod shows that there is no driver loaded
3.) modprobe tells me that there is no 'lib/modules' dir

II.) checking yocto
1.) Bitbake creates a package for my machine ("sama5d3xek") -> there are 
several packages; all are empty except the one with the "kernel-module-" 
prefix
2.) checking the "deploy/images" dir -> the module is not listed at the 
"*.manifest" file
3.) checking the "modules-*.tgz" file -> modules are in(like the ext4.ko) 
but not the ledmodule.ko

As far as I understand yocto and the meta-atmel layer there are "two" 
images build. One is the kernel and it goes under the "work/sama5d3xek..." 
dir. The other one is the rootfs and it goes under the "work/cortexahf..." 
dir. By using the module class for my ledmodule recipe yocto is generating 
it in the kernel dir.
I think I need to tell yocto in some way that it should include the module 
in the kernel(where the bb is placed) or at the rootfs (where the recipe 
is missing).
For me it seems that I have to rewrite my recipe. I delete the module 
class reference and adjust the install path to /lib/modules.
But it looks for me more as an workaround, because adding a own 
driver/module seems a common task which should be supported my yocto. I 
like to know the common way how to do it.

When checking the kernel package for the module the path for it is 
"/lib/modules/4.1.0_linux4sam.../extra/ledmodule.ko". The dir 
"/lib/modules/4.1.0_linux4sam.../" not exits at my target.

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.




Von:"Esponde, Joel" 
An: "s.jar...@esa-grimma.de" , 
"yocto@yoctoproject.org" 
Datum:  13.05.2016 11:15
Betreff:RE: [yocto] how to install a kernel module



Hi,
 
FYI, image recipes are in recipes-core/images folders.
So if you created your own image recipe, my previous mail should answer 
your need.
 
Otherwise, I don’t know if you could just add this line to your local.conf 

[yocto] Antwort: RE: how to install a kernel module

[S . Jaritz]

Thanks for taking the time to help me

I tried your approach but it does not worked.

I tell what I figured out so far:

I.) checking the target system
1.) When flashing the images into my device and boot the system, the 
driver is not loaded.
2.) lsmod shows that there is no driver loaded
3.) modprobe tells me that there is no 'lib/modules' dir

II.) checking yocto
1.) Bitbake creates a package for my machine ("sama5d3xek") -> there are 
several packages; all are empty except the one with the "kernel-module-" 
prefix
2.) checking the "deploy/images" dir -> the module is not listed at the 
"*.manifest" file
3.) checking the "modules-*.tgz" file -> modules are in(like the ext4.ko) 
but not the ledmodule.ko

As far as I understand yocto and the meta-atmel layer there are "two" 
images build. One is the kernel and it goes under the "work/sama5d3xek..." 
dir. The other one is the rootfs and it goes under the "work/cortexahf..." 
dir. By using the module class for my ledmodule recipe yocto is generating 
it in the kernel dir.
I think I need to tell yocto in some way that it should include the module 
in the kernel(where the bb is placed) or at the rootfs (where the recipe 
is missing).
For me it seems that I have to rewrite my recipe. I delete the module 
class reference and adjust the install path to /lib/modules.
But it looks for me more as an workaround, because adding a own 
driver/module seems a common task which should be supported my yocto. I 
like to know the common way how to do it.

When checking the kernel package for the module the path for it is 
"/lib/modules/4.1.0_linux4sam.../extra/ledmodule.ko". The dir 
"/lib/modules/4.1.0_linux4sam.../" not exits at my target.

Regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Esponde, Joel" 
An: "s.jar...@esa-grimma.de" , 
"yocto@yoctoproject.org" 
Datum:  13.05.2016 11:15
Betreff:RE: [yocto] how to install a kernel module



Hi,
 
FYI, image recipes are in recipes-core/images folders.
So if you created your own image recipe, my previous mail should answer 
your need.
 
Otherwise, I don’t know if you could just add this line to your local.conf 
file…
 
IMAGE_INSTALL_append = " ledmodule"
 
The best way to know that your IMAGE_INSTALL variable is correctly set is 
to call this bitbake command:
 
$ bitbake  -e
 
Bitbake will output all the build environment variables and functions 
related to your image recipe.
So you will be able to check with this command that IMAGE_INSTALL has 
effectively your module name added to the list.
 
bitbake -e is a very important command when working with Yocto.
 
Regards,
 
Joël Esponde
Honeywell | Sensing and Productivity Solutions
 
De : yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org
] De la part de s.jar...@esa-grimma.de
Envoyé : jeudi 12 mai 2016 16:32
À : yocto@yoctoproject.org
Objet : [yocto] how to install a kernel module
 
Hej 

I created a recipe for a own modul. It's similar to the example given at: 

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod
 


I checked the bitbake process. A "kernel-module-" package is 
created and filled with the ko-file. 

Actually I am failing to bring the module into my image and run it. Are 
there a special command for the "local.conf" or so? 

How and where to include the module? 

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie 

[yocto] how to install a kernel module

[S . Jaritz]

Hej

I created a recipe for a own modul. It's similar to the example given at:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod

I checked the bitbake process. A "kernel-module-" package is 
created and filled with the ko-file.

Actually I am failing to bring the module into my image and run it. Are 
there a special command for the "local.conf" or so?

How and where to include the module?

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] at91 kernel module problem with includes

[S . Jaritz]

Hej 

I like to build a module. I am working on a SAMA5D3x Evalboard form Atmel. 
For that I use the meta-atmel recipes.

My driver should toggle a pin. The pins are defined in the "mach/gpio.h". 
Any ideas how to configure that the atmel linux is creating the includes? 
Maybe I forgot to set some parameter at the local.conf?

Kind regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: How to build a simple kernel modul

[S . Jaritz]

Thanks so far!

I have 3 questions for my understanding:

1.) How to define extra Include Paths if the module needs some extra 
Includes?
Like the "mach/gpio.h", which should be under 
"/arch/arm/mach-at91/include" and is needed for the PIN 
definitions.
Should it be done at the Makefile like:
CFLAGS_hello.o +=  -I${COMPILER_INCLUDE} 
-I${KERNEL_DIR}/arch/arm/mach-at91/include
1.1) What are the equivalents to ${COMPILER_INCLUDE} and 
${KERNEL_DIR} in Yocto?
1.2) Should it be done in the Makefile or at the bb-File?
2.) How to activate/deactivate the Driver in the "local.conf"?
3.) How does the process works with cmake?
3.1) Is it enough to inherit after modul cmake?
like @ hello-mod_0.1.bb -> "inherit module cmake"


With kind regards!

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Esponde, Joel" 
An: "pet...@technux.se" , "yocto@yoctoproject.org" 

Datum:  10.05.2016 12:30
Betreff:Re: [yocto] How to build a simple kernel modul
Gesendet von:   yocto-boun...@yoctoproject.org



Hi,
 
And here is a hello world module example:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod
 
Joël Esponde
Honeywell | Sensing and Productivity Solutions
 
De : yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org
] De la part de Petter Mabäcker
Envoyé : mardi 10 mai 2016 06:51
À : yocto@yoctoproject.org
Objet : Re: [yocto] How to build a simple kernel modul
 
2016-05-09 17:06 skrev s.jar...@esa-grimma.de:
Hej, 

I want to build a recipe for a simple GPIO Module. I found no tutorial at 
the documentation. What is the comon way to build a simple kernel module? 

The Makefile looks like: 
# 
obj-m += ledmodule.o 

SRC := $(shell pwd) 

all: modules 

modules: 
$(MAKE) -C $(KERNEL_SRC) M=$(SRC) modules 

modules_install: 
$(MAKE) -C $(KERNEL_SRC) M=$(SRC) modules_install 

clean: 
rm -rf *.o *.ko *.mod.c 
# 
The recipe contains: 
# 
SUMMARY = "ledmodule" 
SECTION = "" 
LICENSE = "CLOSED" 

inherit module 

SRC_URI = "file://ledmodule.c \ 
file://Makefile \ 
" 
S = "${WORKDIR}/ledmodule-0.1" 
# 

Regards

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.
Hi,

There are actually some guides for this, see lab4 in:
https://www.yoctoproject.org/sites/default/files/kernel-lab-2.1_0.pdf
But to simply build a module using bitbake, you can just do:
$ bitbake ledmodule
then you will find your recipe and the module in the ./tmp/work/ structure 
(assuming you are not inheriting 'rm_work' in local.conf...).
 
if you just want to compile it, you can run:
$ bitbake ledmodule -c compile
 
BR Petter
Petter Mabäcker
 
Technux 
www.technux.se-- 
___
yocto 

[yocto] How to build a simple kernel modul

[S . Jaritz]

Hej,

I want to build a recipe for a simple GPIO Module. I found no tutorial at 
the documentation. What is the comon way to build a simple kernel module?

The Makefile looks like:
#
obj-m += ledmodule.o

SRC := $(shell pwd)

all: modules

modules:
$(MAKE) -C $(KERNEL_SRC) M=$(SRC) modules

modules_install:
$(MAKE) -C $(KERNEL_SRC) M=$(SRC) modules_install

clean:
rm -rf *.o *.ko *.mod.c
#
The recipe contains:
#
SUMMARY = "ledmodule"
SECTION = ""
LICENSE = "CLOSED"

inherit module

SRC_URI = "file://ledmodule.c \
file://Makefile \
"
S = "${WORKDIR}/ledmodule-0.1"
#

Regards

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] HG Parameters for the fetcher

[S . Jaritz]

Thanks,

What is when the HG comes over SSH with authentication? Like:

SRC_URI = "hg://myHG/ABC;module="dev";protocol=ssh;rev=42"

with user for example "yocto"

I think the syntax could be: SRC_URI = 
"hg://yocto@myHG/ABC;module="dev";protocol=ssh;rev=42"

Regards

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Jeyachandran, Yukatharsani (Contractor)" 

An: "s.jar...@esa-grimma.de" , yocto 

Datum:  02.05.2016 16:50
Betreff:Re: [yocto] HG Parameters for the fetcher



Hi,

Add your source file in this below format:-

For Example:-

SRCREV = "${AUTOREV}"
SRC_URI = "svn or git ://;module=" ";protocol=https or ssh"

Thanks and Regards,
Yukatharsani J.

From: yocto-boun...@yoctoproject.org  on 
behalf of s.jar...@esa-grimma.de 
Sent: Monday, May 2, 2016 9:25 AM
To: yocto
Subject: [yocto] HG Parameters for the fetcher 
 
Hej, 

Actually I try to build a recipe for a Mercurial SCM. The hg sources are 
local. In my bb File I have this lines: 


SRCREV = "486c7001d4e5" 
SRC_URI = "hg://myHG" 

I got the error: 

ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/myHG/0.1-r0/temp/log.do_fetch.27908
 

Log data follows: 
| DEBUG: Executing python function do_fetch 
| DEBUG: Executing python function base_do_fetch 
| DEBUG: Python function base_do_fetch finished 
| DEBUG: Python function do_fetch finished 
| ERROR: Function failed: URL: 'hg://myHG' is missing the required 
parameter 'module' 
ERROR: Task 4 
(/home/user/myTC/poky/meta-sek4/recipes-test/deamons/myHG_0.1.bb, 
do_fetch) failed with exit code '1' 


Any ideas?

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] HG Parameters for the fetcher

[S . Jaritz]

Hej,

Actually I try to build a recipe for a Mercurial SCM. The hg sources are 
local. In my bb File I have this lines:


SRCREV = "486c7001d4e5"
SRC_URI = "hg://myHG"

I got the error:

ERROR: Logfile of failure stored in: 
/home/user/myTC/poky/build/tmp/work/cortexa5hf-vfp-poky-linux-gnueabi/myHG/0.1-r0/temp/log.do_fetch.27908
Log data follows:
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Function failed: URL: 'hg://myHG' is missing the required 
parameter 'module'
ERROR: Task 4 
(/home/user/myTC/poky/meta-sek4/recipes-test/deamons/myHG_0.1.bb, 
do_fetch) failed with exit code '1'


Any ideas?

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: Re: Antwort: Re: how to configure the build packages of a makefile based libary

[S . Jaritz]

Hej

Finally we made it - Thanks to you all for helping me! I attached my bb 
file for that case someone is searching for a bitbake recipe for building 
the libhiredis

##
SUMMARY = "libhiredis"
SECTION = "lib"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=d84d659a35c666d23233e54503aaea51"

# 0.13.3
# SRCREV = "010756025e8cefd1bc66c6d4ed3b1648ef6f1f95"
SRC_URI = "git://github.com/redis/hiredis.git;rev=v0.13.3"

S = "${WORKDIR}/git/"

# error handleing
# @PREFIX: set the path from /usr/local to /usr/
# @INSTALL: set the copy instruction from "cp -a" to "cp -r"
EXTRA_OEMAKE = "'PREFIX=${prefix}' 'INSTALL=''cp -r'''"

do_compile() {
oe_runmake all 'CC=${CC}'
}

do_install() {
oe_runmake install 'DESTDIR=${D}'
}
##

regards

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Burton, Ross" 
An: s.jar...@esa-grimma.de
Kopie:  "yocto@yoctoproject.org" , YUKATHARSANI 
JEYACHANDRA 
Datum:  29.04.2016 10:59
Betreff:Re: Re: [yocto] Antwort: Re: how to configure the build 
packages of a makefile based libary



Hi Stefan,

So close :)  Some more points:

On 29 April 2016 at 08:54,  wrote:
> LICENSE = "COPYING"

This should be the name of the license itself, not the filename.  Looks a 
bit like MIT to me.
 
> LIC_FILES_CHKSUM = "file://$
{WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"

This URI is relative to ${S} so you can just do file://COPYING;md5=
 
> EXTRA_OEMAKE = "'PREFIX=/usr/'" 

Use PREFIX=${prefix} to respect the what the distro has configured.  
Annoyingly you can't override the other paths such a libdir easily, so 
this will break in multilib configurations or if I recall correctly, on 
aarch64.

The commandline outputs: 
# 
NOTE: Executing RunQueue Tasks 
WARNING: QA Issue: libhiredis: /libhiredis-staticdev/usr/lib/libhiredis.a 
is owned by uid 1000, which is the same as the user running bitbake. This 
may be due to host contamination [host-user-contaminated] 
WARNING: QA Issue: libhiredis: /libhiredis/usr/lib/libhiredis.so.0.13 is 
owned by uid 1000, which is the same as the user running bitbake. This may 
be due to host contamination [host-user-contaminated] 
WARNING: QA Issue: libhiredis: 
/libhiredis-dev/usr/lib/pkgconfig/hiredis.pc is owned by uid 1000, which 
is the same as the user running bitbake. This may be due to host 
contamination [host-user-contaminated] 
#  

The upstream Makefile is using "cp -a" which preserves ownership, so as 
you built the package the files are owned by you.  Luckily you can 
override this by passing "INSTALL='cp -r' to the make install (they use cp 
to recursively copy directories, so you need to pass -r instead).

I've a recipe locally with these changes and it builds without warnings 
and is packaged correctly.

This is what happens when maintainers think autotools is too complicated 
and a bare makefile is just fine: they do it wrong. :)

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

[yocto] Antwort: Re: how to configure the build packages of a makefile based libary

[S . Jaritz]

Hej

sorry - that does not work. Maybe you can show me some working/common 
code.

Do I have to create the FILE_${PV} or/and FILE_${PV}-dev, 
FILE_${PV}-static?

The builded files go into the Git dir & the autotools-brokensep is 
generating the package dir. I repeat my question: What are the commands in 
the bb file to build the packages (release, static, dev, whatever ...)?

Sorry - I do not understand at all the steps and theire parameters to 
build a libary. Is there somewhere an example given?

Below my bb file and the console error print.

 libhiredis 
SUMMARY = "libhiredis"
SECTION = "sek4"
LICENSE = "COPYING"
LIC_FILES_CHKSUM = "file://$
{WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"

# 0.13.3
# SRCREV = "010756025e8cefd1bc66c6d4ed3b1648ef6f1f95"
SRC_URI = "git://github.com/redis/hiredis.git;rev=v0.13.3"

S = "${WORKDIR}/git/"

# we need to pass the Cxx parameter extra to the make call
EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} 
-I${S}/include' 'BUILDDIR=${S}' 'DESTDIR=${D}'"

inherit autotools-brokensep

do_compile() {
oe_runmake all 'CC=${CC}'
}

do_install() {
oe_runmake install 'DESTDIR=${D}'
}
FILES_${PN} += "/user/local"


### consol error ###
ERROR: QA Issue: libhiredis: Files/directories were installed but not 
shipped in any package:
  /usr/local
  /usr/local/lib
  /usr/local/include
  /usr/local/lib/libhiredis.so
  /usr/local/lib/libhiredis.so.0.13
  /usr/local/lib/libhiredis.a
  /usr/local/lib/.debug
  /usr/local/lib/pkgconfig
  /usr/local/lib/.debug/libhiredis.so.0.13
  /usr/local/lib/pkgconfig/hiredis.pc
  /usr/local/include/hiredis
  /usr/local/include/hiredis/sds.h
  /usr/local/include/hiredis/read.h
  /usr/local/include/hiredis/async.h
  /usr/local/include/hiredis/hiredis.h
  /usr/local/include/hiredis/adapters
  /usr/local/include/hiredis/adapters/glib.h
  /usr/local/include/hiredis/adapters/macosx.h
  /usr/local/include/hiredis/adapters/libev.h
  /usr/local/include/hiredis/adapters/libevent.h
  /usr/local/include/hiredis/adapters/qt.h
  /usr/local/include/hiredis/adapters/libuv.h
  /usr/local/include/hiredis/adapters/ae.h
  /usr/local/include/hiredis/adapters/ivykis.h
Please set FILES such that these items are packaged. Alternatively if they 
are unneeded, avoid installing them or delete them within do_install.
libhiredis: 24 installed and not shipped files. [installed-vs-shipped]
NOTE: Tasks Summary: Attempted 388 tasks of which 375 didn't need to be 
rerun and all succeeded.

Mit freundlichen Grüßen

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to configure the build packages of a makefile based libary

[S . Jaritz]

Hej

The makefile has an install section. I relocated it with the ${D}. By 
doing that I managed that the compiler filled the "package" directory. But 
there is still a packing issue.
Below is the log (and below of it is the libhiredis.bb).

Now my question: How to define the FILES variable for a proper packing?

 log ##
NOTE: Executing RunQueue Tasks
WARNING: libhiredis: No generic license file exists for: COPYING in any 
provider
ERROR: QA Issue: libhiredis: Files/directories were installed but not 
shipped in any package:
  /usr/local
  /usr/local/lib
  /usr/local/include
  /usr/local/lib/libhiredis.so
  /usr/local/lib/libhiredis.so.0.13
  /usr/local/lib/libhiredis.a
  /usr/local/lib/.debug
  /usr/local/lib/pkgconfig
  /usr/local/lib/.debug/libhiredis.so.0.13
  /usr/local/lib/pkgconfig/hiredis.pc
  /usr/local/include/hiredis
  /usr/local/include/hiredis/sds.h
  /usr/local/include/hiredis/read.h
  /usr/local/include/hiredis/async.h
  /usr/local/include/hiredis/hiredis.h
  /usr/local/include/hiredis/adapters
  /usr/local/include/hiredis/adapters/glib.h
  /usr/local/include/hiredis/adapters/macosx.h
  /usr/local/include/hiredis/adapters/libev.h
  /usr/local/include/hiredis/adapters/libevent.h
  /usr/local/include/hiredis/adapters/qt.h
  /usr/local/include/hiredis/adapters/libuv.h
  /usr/local/include/hiredis/adapters/ae.h
  /usr/local/include/hiredis/adapters/ivykis.h
Please set FILES such that these items are packaged. Alternatively if they 
are unneeded, avoid installing them or delete them within do_install.
libhiredis: 24 installed and not shipped files. [installed-vs-shipped]
NOTE: Tasks Summary: Attempted 388 tasks of which 375 didn't need to be 
rerun and all succeeded.

Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
 end of log ##

 libhiredis ##
SUMMARY = "libhiredis"
SECTION = "sek4"
LICENSE = "COPYING"
LIC_FILES_CHKSUM = "file://$
{WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"

# 0.13.3
# SRCREV = "010756025e8cefd1bc66c6d4ed3b1648ef6f1f95"
SRC_URI = "git://github.com/redis/hiredis.git;rev=v0.13.3"

S = "${WORKDIR}/git/"

# we need to pass the Cxx parameter extra to the make call
EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} 
-I${S}/include' 'BUILDDIR=${S}' 'DESTDIR=${D}'"

inherit autotools-brokensep

do_compile() {
oe_runmake all 'CC=${CC}'
}

do_install() {
oe_runmake install 'DESTDIR=${D}'
}
 libhiredis of log ##


with kind regards

Stefan Jaritz

Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.



Von:"Burton, Ross" 
An: s.jar...@esa-grimma.de
Kopie:  "yocto@yoctoproject.org" 
Datum:  28.04.2016 12:52
Betreff:Re: [yocto] how to configure the build packages of a 
makefile based libary




On 28 April 2016 at 10:50,  wrote:
I like to include the hiredis library. I created a recipe and modified the 
EXTRA_OEMAKE. The compilation works (in the git directory object, "so" and 
"a" files are generated). But the generated files are not placed into 
packages. 

Any ideas? 

You need to look at the makefile to see if it has an install target, and 
if it does what it's called, and if it has a way of controlling where 
files actually go (both respecting $prefix instead of /usr, and letting 
you relocate via ${D} so it doesn't try and install to /usr on your build 
machine).  If it does all of those right then you can write a do_install() 
that just calls the right make commands.  Chances are that it does 
something wrong and it's easier to just write a do_install() that creates 
directories and copies files manually.

This is why it doesn't happen automatically unless you're using something 
like automake - there's no standard way.

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

[yocto] how to configure the build packages of a makefile based libary

[S . Jaritz]

Hej

I like to include the hiredis library. I created a recipe and modified the 
EXTRA_OEMAKE. The compilation works (in the git directory object, "so" and 
"a" files are generated). But the generated files are not placed into 
packages.

Any ideas?

below there is the "libhiredis.bb" file:
#
SUMMARY = "libhiredis"
SECTION = "sek4"
LICENSE = "COPYING"
LIC_FILES_CHKSUM = "file://$
{WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"

# 0.13.3
# SRCREV = "010756025e8cefd1bc66c6d4ed3b1648ef6f1f95"
SRC_URI = "git://github.com/redis/hiredis.git;rev=v0.13.3"

S = "${WORKDIR}/git/"

# we need to pass the Cxx parameter extra to the make call
EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} 
-I${S}/include' 'BUILDDIR=${S}'"
#

Regards!
Stefan


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] problems with cmake finding the c++ includes

[S . Jaritz]

Hej,

I am new to yocto. I like to create an recipe for the g3log library. I 
managed to get the git sources and start the cmake compile. But it stops 
when it tries to compile "#include ". Do you have an idea how to 
fix that?

Below there is the content of the "g3log.bb":

SUMMARY = "g3log"
SECTION = "sek4"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://$
{COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

DEPENDS ="boost"

SRC_URI[md5sum] = "0dd4767bd072159e64ad69052bb1dbba"
SRC_URI[sha256sum] = 
"4fbcc9afe24f6d8b5b90ff04481e88dd0b34f6a797825dab02cd88f129d3ccb7"

SRC_URI = "git://github.com/KjellKod/g3log.git;rev=1.2"

S = "${WORKDIR}/git"

inherit pkgconfig cmake

 

Mit freundlichen Grüßen

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Binary Configuration Support

[S . Jaritz]

Hej,

I read that there is a way to the binary configuration (
https://wiki.yoctoproject.org/wiki/Binary_configuration_support). It is 
described jow this internally works. But I am missing an example how to 
use it praticaly.

My learning system is a SAMA5D3x Eval board from Atmel. For that I am 
using the meta-atmel layer to generate an kernel + rootfs. Now I want to 
configure the network to static IPs etc. For me the binary support seems 
designed for that.

Can you explain me, how to use it?

http://stackoverflow.com/questions/36764613/how-to-configurate-yocto-builds-by-useing-the-binary-configuration

Kind regards!

Stefan Jaritz



ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese 
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser 
Mail 
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you 
are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is 
strictly 
forbidden.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto