[yocto] Taskhash mismatch when using WIC-tool

[Keskinarkaus, Teemu]

Hi,

I recently started using WIC-tool to create the final image instead and from 
day one I seem to be having taskhash mismatch errors when first time creating 
the image. If I run the same command second time it goes through without any 
problems.

I'm using Yocto 2.1.

Here is the error I'm talking about:

ERROR: release-image-1.0-r0 do_rootfs_wicenv: Taskhash mismatch 
da155888bd9c40e3ca6c8584a4d86cf5 verses 8307d09291312e835bb5254c93af3e05 for 
//release-image.bb.do_rootfs_wicenv

Is this known issue or what am I doing wrong?

-TeemuK



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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

[yocto] List of packages in image and their Licenses

[Keskinarkaus, Teemu]

Hi,

I know that there is bitbake command/option to get list of all packages 
available, but how would I get a list of packages that goes to any specific 
image? And is there a way to get what Licenses those packages are using?

-TeemuK



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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

Re: [yocto] UTF-89 support

[Keskinarkaus, Teemu]

Hi,

I tried that. I have now these lines in the local.conf

GLIBC_GENERATE_LOCALES = "en_GB en_US en_GB.UTF-8 en_US.UTF-8"
IMAGE_LINGUAS = "en-gb en-us"

I had to add the "en-us" to IMAGE_LINGUAS or I would only get en_GB locale and 
not en_US at all. Still missing the UTF-8 locales though.

Teemu Keskinarkaus
Software system engineer
CrossControl
making machines smart, safe and productive


-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: 7. marraskuuta 2016 22:12
To: Paul Eggleton
Cc: yocto@yoctoproject.org; Keskinarkaus, Teemu
Subject: Re: [yocto] UTF-89 support

On Mon, Nov 7, 2016 at 11:48 AM, Paul Eggleton <paul.eggle...@linux.intel.com> 
wrote:
> On Mon, 07 Nov 2016 09:24:18 Khem Raj wrote:
>> On 11/7/16 3:48 AM, Keskinarkaus, Teemu wrote:
>> > Hi,
>> >
>> >
>> >
>> > I tried googling this and reading the manual, but I guess this is
>> > too trivial or I’m doing something wrong.
>> >
>> >
>> >
>> > I’m trying to get UTF-8 support to my image. UTF-8 locale more specific.
>> > If I run locale –a command I get these locales listed:
>> >
>> > C
>> >
>> > POSIX
>> >
>> > en_GB
>> >
>> > en_US
>> >
>> >
>> >
>> > I added this line to my local.conf:
>> >
>> > GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 en_US.UTF-8 en_GB en_US"
>>
>> you also need to set IMAGE_LINGUAS to include it into image e.g.
>>
>> GLIBC_GENERATE_LOCALES = "en-gb"
>
> I guess you meant IMAGE_LINGUAS = "en-gb"

yes thanks for noting

>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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

[yocto] UTF-89 support

[Keskinarkaus, Teemu]

Hi,

I tried googling this and reading the manual, but I guess this is too trivial 
or I'm doing something wrong.

I'm trying to get UTF-8 support to my image. UTF-8 locale more specific. If I 
run locale -a command I get these locales listed:
C
POSIX
en_GB
en_US

I added this line to my local.conf:
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 en_US.UTF-8 en_GB en_US"

That didn't bring UTF-8 locales although by looking at the comment I would 
assume they should be already there?  I'm not entirely sure why the UTF-8 
locales are still missing and how do I get them there?


Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.crosscontrol.com
CrossControl
making machines smart, safe and productive




Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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

[yocto] [prelink-cross] Prelinking to wrong library ld-linux.so.3 instead ld-linux-armhf.so.3

[Keskinarkaus, Teemu]

Hi,

As the subject states, I'm having that problem with Yocto. I'm using Yocto 1.7 
and already updated the prelink-cross to latest version.  This happens only on 
the applications I've added myself. The actual Yocto applications compiles just 
fine. I don't have any autoconf in use with my applications so I'm not sure if 
that has anything to do with the prelink issue.

As a workaround I've made symbolic link from /lib/ld-linux-armhf.so.3 to 
/lib/ld-linux.so.3, but I would like to solve the actual problem.

With Yocto 1.7 default prelink I get following errors to log.do_rootfs:

build/tmp/sysroots/i686-linux/usr/sbin/prelink: /usr/bin/weston-terminal: Using 
/lib/ld-linux-armhf.so.3, not /lib/ld-linux.so.3 as dynamic linker

With latest prelink I get following errors in that log:

/build/tmp/sysroots/i686-linux/usr/sbin/prelink: /usr/bin/testapplication: 
Could not parse ` /build/tmp/sysroots/i686-linux/usr/sbin//prelink-rtld: error 
while loading shared libraries: ld-linux-armhf.so.3'

So with old version the prelink is using the proper library for existing Yocto 
applications, but my application is missing from that list. And with latest 
application only my application is listed with not founding the library it 
should.  Why it's only on those recipes I've created? I've looked some existing 
recipes and they don't have any prelink references. In local.conf I have 
"image-prelink" defined in USER_CLASSES.

I found someone else having issues with prelink as well, but didn't find any 
solution that would work for me since it seems to happen only on 
applications/recipes that I've made.

Here is the recipe for testapplication:

--
LICENSE = "LGPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
PR = "r15"

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

inherit localapp

EXTRA_OEMAKE = " \
CC_PREFIX=arm-poky-linux-gnueabi- \
"

--


Localapp changes the source directory so sources can be locally.

--
inherit base externalsrc

EXTERNALSRC = "${COREBASE}/../apps/${PN}"
EXTERNALSRC_BUILD = "${EXTERNALSRC}"
--

Teemu Keskinarkaus
Software system engineer





Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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

[yocto] Toolchain and SDK

[Keskinarkaus, Teemu]

Hi,

I'm sure (or at least hope so) that there is documentation for this, but I just 
couldn't find it.

We are using Yocto to build Linux images on couple different HW (x86 and imx6). 
Now we would like to make SDK (with toolchain) for them.

I've learned that there is command: bitbake image-recipe -c populate_sdk 
that'll create the sdk. The thing is that it contains the sysroots, but 
toolchain is not there.

I tried meta-toolchain - target as well, but that too didn't make the toolchain 
or at least I couldn't find it anywhere.

How should I do the sdk that it comes with the toolchain also? I'm using Yocto 
versions 1.6.1 and 1.7.1.

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.comhttp://www.maximatecc.com/

maximatecc
making machines smart, safe and productive




Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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

Re: [yocto] Toolchain and SDK

[Keskinarkaus, Teemu]

Yeah, I forgot that I need to be more precise here. Of course I'm using the 
actual recipe name and not the 'image-recipe'.

It turns out that the toolchain was included after all. Just took me awhile to 
find it there since it was so well hidden there!

Teemu Keskinarkaus
Software system engineer

maximatecc
making machines smart, safe and productive


 -Original Message-
 From: Trevor Woerner [mailto:twoer...@gmail.com]
 Sent: 12. toukokuuta 2015 1:03
 To: Keskinarkaus, Teemu; yocto@yoctoproject.org
 Subject: Re: [yocto] Toolchain and SDK

 On 05/11/15 03:52, Keskinarkaus, Teemu wrote:
 
 
  I've learned that there is command: bitbake image-recipe -c
  populate_sdk that'll create the sdk. The thing is that it contains the
  sysroots, but toolchain is not there.
 

 Just to clarify, you're not literally typing bitbake image-recipe -c 
 populate_sdk,
 are you? The image-recipe part should be replaced with the actual image 
 string
 you want the generate an SDK for. For example, if you were building bitbake
 core-image-minimal, then you generate its SDK with bitbake core-image-
 minimal -c populate_sdk.

 
 
  I tried meta-toolchain - target as well, but that too didn't make the
  toolchain or at least I couldn't find it anywhere.
 

 Have you looked in $TMPDIR/.../deploy/.../sdk ? (different version and/or
 different distros put it in different places, but looking for an sdk 
 directory
 beneath a deploy directory is your best bet)



Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this email is not an intended 
recipient, you have received this email in error and any review, dissemination, 
distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately 
by return mail and permanently delete the copy you received.

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