[yocto] [meta-java][PATCH] commons-collections3: upgrade from 3.2.1 to 3.2.2

[Zhenhua Luo]

Signed-off-by: Zhenhua Luo <zhenhua@nxp.com>
---
 .../{commons-collections3_3.2.1.bb => commons-collections3_3.2.2.bb} | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
 rename recipes-core/jakarta-commons/{commons-collections3_3.2.1.bb => 
commons-collections3_3.2.2.bb} (63%)

diff --git a/recipes-core/jakarta-commons/commons-collections3_3.2.1.bb 
b/recipes-core/jakarta-commons/commons-collections3_3.2.2.bb
similarity index 63%
rename from recipes-core/jakarta-commons/commons-collections3_3.2.1.bb
rename to recipes-core/jakarta-commons/commons-collections3_3.2.2.bb
index 852cac7..0a53d09 100644
--- a/recipes-core/jakarta-commons/commons-collections3_3.2.1.bb
+++ b/recipes-core/jakarta-commons/commons-collections3_3.2.2.bb
@@ -1,5 +1,6 @@
 require jakarta-commons.inc
 
+LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
 PR = "${INC_PR}.1"
 
 DESCRIPTION = "A set of abstract data type interfaces and implementations that 
offer a wealth of useful functionality and a solid foundation for extending 
that functionality"
@@ -9,5 +10,5 @@ SRC_URI = 
"http://www.apache.org/dist/commons/collections/source/commons-collect
 S = "${WORKDIR}/commons-collections-${PV}-src"
 
 
-SRC_URI[md5sum] = "031ce05872ddb0462f0dcce1e5babbe9"
-SRC_URI[sha256sum] = 
"9a4a800cb7ecdaf3b6f608cd608682b88b506f1b1c4b727d15471ae3329fc63d"
+SRC_URI[md5sum] = "776b51a51312c1854ad8f6d344a47cda"
+SRC_URI[sha256sum] = 
"070d94fe77969d8949bd129a618e6a7bee6b83b5b5db3ef3f983395a5428b914"
-- 
2.9.3

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

Re: [yocto] fetcher failure

[Zhenhua Luo]

I have submitted a patch for the fetch issue, can you please give a try? You 
can use master-next branch of meta-fsl-ppc for the validation.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Anicic Damir (PSI)
Sent: Tuesday, September 27, 2016 5:34 PM
To: Chris Z. 
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] fetcher failure

Why should I check,
the meta-fsl-ppc/recipes-kernel/linux/linux-qoriq_4.1.bb has

SRC_URI = "git://git.freescale.com/ppc/sdk/linux.git;branch=sdk-v2.0.x \
SRCREV = "bd51baffc04ecc73f933aee1c3a37c8b44b889a7"

If that is wrong freescale should correct it.

And besides, the downloaded file gets deleted.

But, OK, I'll try.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Freescale DPAA drivers

[Zhenhua Luo]

I guess you are using the community kernel instead of NXP SDK kernel, the DPAA 
upstream is ongoing currently, to use the full function DPAA drivers, you can 
use the kernel recipes in meta-fsl-ppc 
layer(http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/log/).


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Anicic Damir (PSI)
Sent: Friday, September 23, 2016 10:14 PM
To: yocto@yoctoproject.org
Subject: [yocto] Freescale DPAA drivers

Hi,

I am using Yocto 2.1, PowerPC64, default kernel 4.1.22
Building for T2080rdb.

Everything builds, but kernel is missing DPAA Freescale drivers
(dpaa_eth at least)


It seems that DPAA Freescale drivers not in any Linux kernel (or am I wrong).

Why is that so, is Freescale not planing to include them in kernel ?

Kind regards,

Damir


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

Re: [yocto] Cortex-M4 build support

[Zhenhua Luo]

Thank you so much for your suggestion, Trevor. 


Best Regards, 

Zhenhua

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Trevor Woerner
> Sent: Friday, September 16, 2016 4:07 AM
> To: Khem Raj 
> Cc: robert.berger@gmane ;
> yocto@yoctoproject.org; yocto-
> EtnWKYl6rD/WsZ/bqmp...@public.gmane.org  EtnWKYl6rD/WsZ/bqmp...@plane.gmane.org>
> Subject: Re: [yocto] Cortex-M4 build support
> 
> On Tue 2016-09-13 @ 01:15:49 PM, Khem Raj wrote:
> >
> > > On Sep 13, 2016, at 10:31 AM, robert.berger@gmane
>  wrote:
> > >
> > > Hi,
> > >
> > > Shouldn't it be possible to build a bare-metal Cortex-M4 compiler with 
> > > the YP
> and build a small RTOS like FreeRTOS with this compiler?
> > >
> >
> > yes it should be possible. you can also look into meta-ti where I
> > think they try to have their DSP toolchain build some code using OE
> > recipe model
> 
> Perhaps other things to consider (I'm not entirely sure if these apply, but 
> maybe
> worth investigating?)
> 
> The ROS project has a meta layer:
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-ros/
> 
> If your CortexM board has enough RAM (e.g. http://www.emcraft.com/) you
> can run (a version of) Linux (uClinux) right on your CortexM target:
> https://github.com/EmcraftSystems/linux-emcraft
> 
> The Emcraft website appears to provide Linux support for NXP-based CortexM
> boards too: http://www.emcraft.com/products/456
> http://www.emcraft.com/products/88
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding mysql in bitbaking meta-toolchain-qt5

[Zhenhua Luo]

The package name is mariadb instead of mysql, If you need the mysql headers, 
you should add libmysqlclient-dev.

More details of mariadb packaging can be found in 
meta-openembedded/meta-oe/recipes-support/mysql/mariadb.inc.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ambika
Sent: Wednesday, September 14, 2016 3:29 PM
To: yocto@yoctoproject.org
Subject: [yocto] Adding mysql in bitbaking meta-toolchain-qt5

Hello,

I’m doing bitbake of meta-toolchain-qt5. When trying to use mysql, not able to 
find it in include/ directory.

mysql sources is located in the below path in my yocto setup,

sources/meta-openembedded/meta-oe/recipes-support/mysql

Tried to include mysql by adding the below to conf/local.conf under build 
directory but could not able to locate mysql under include/.
(Also not sure whether I’m doing it right.)

IMAGE_INSTALL_append = ”mysql”

Can anyone please let me know the procedure to include mysql to the 
meta-toolchain-qt5.

Thanks in Advance.

Regards,
Ambika.



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

Re: [yocto] Cortex-M4 build support

[Zhenhua Luo]

Hi Mark, 

Thanks a lot for your comments. 

Is there plan to support non-MMU targets in Yocto? 


Best Regards,

Zhenhua

> -Original Message-
> From: Mark Hatle [mailto:mark.ha...@windriver.com]
> Sent: Friday, September 09, 2016 10:37 PM
> To: Zhenhua Luo <zhenhua@nxp.com>; 'yocto@yoctoproject.org'
> <yocto@yoctoproject.org>
> Subject: Re: [yocto] Cortex-M4 build support
> 
> On 9/9/16 2:58 AM, Zhenhua Luo wrote:
> > Hi all,
> >
> >
> >
> > Can Yocto support image build for Cortex-M4 targets? If no, does
> > somebody know if there is some distro/packaging tool which can support
> Cortex-M4?
> >
> 
> The Cortex-M4 does not have an MMU.  The Yocto Project system, currently,
> only supports MMU based architectures.
> 
> If Linux is a requirement for you, you will need to find a non-MMU based
> uClinux system to work with.
> 
> Otherwise there are a number of other embedded OSs for MMU-less targets
> that may be more appropriate to the memory and system constraints of the M
> series CPUs.
> 
> --Mark
> 
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Zhenhua
> >
> >
> >

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

[yocto] Cortex-M4 build support

[Zhenhua Luo]

Hi all,

Can Yocto support image build for Cortex-M4 targets? If no, does somebody know 
if there is some distro/packaging tool which can support Cortex-M4?


Best Regards,

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

Re: [yocto] profiling tools on a T4240RDB board

[Zhenhua Luo]

The fsl-image-minimal rootfs doesn't include those graphic packages by default, 
I think those packages are included by the dependency of new added packages.

You can run "bitbake -g fsl-image-minimal" to generate the dependence file and 
analysis how the unneeded packages are brought in.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Leonardo Sandoval
Sent: Wednesday, August 24, 2016 10:19 PM
To: Tanasa Bogdan ; 'yocto@yoctoproject.org' 

Subject: Re: [yocto] profiling tools on a T4240RDB board




El 08/24/2016 a las 04:01 AM, Tanasa Bogdan escribió:
Hi,

We are using the (freescale) linux yocto 1.6 on a T4240RDB board where we want 
to have "tools-profile" set in our local.conf file. When building the 
fsl-image-minimal we see that there are some packages that are graphics-related 
(like gtk+, pixbuf, etc..). The card does not have any graphics capabilities. 
Why does these packets install at all? Is it possible to have the profiling 
tools without any gtk dependencies? How the local.conf should look like?
I believe the image you are using include those graphic-related pkgs so that is 
why you are seeing them. You may redefine your image, at the end 
fsl-image-minimal is just an example that you can modify. Also you may have 
more answers  on a FSL (NXP?) channel/mailing-list



PS: These dependencies are there even when we choose tools-sdk in order to have 
gcc in the final image.

Thanks,
Bogdan.



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

Re: [yocto] Yocto rootfs to support auto-login or remove the login prompt

[Zhenhua Luo]

Thanks a lot, Daniel, 

I will give a try. 


Best Regards,

Zhenhua

> -Original Message-
> From: Daniel. [mailto:danielhi...@gmail.com]
> Sent: Wednesday, August 03, 2016 9:10 AM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Yocto rootfs to support auto-login or remove the login
> prompt
> 
> I don't know if Yocto has something more standard but, you may edit
> /etc/inittab to spawn something other than getty. You can achieve this by
> ROOTFS_POSTPROCESS_COMMAND.
> 
> Take at look at this ancient link:
> http://www.tldp.org/LDP/sag/html/config-init.html
> 
> 2016-08-02 5:46 GMT-03:00 Zhenhua Luo <zhenhua@nxp.com>:
> > Hi,
> >
> >
> >
> > I want to generate a rootfs image which can skip the Linux login
> > prompt or auto-login Linux? Is it possible in Yocto? If yes, may I
> > know how to implement it?
> >
> >
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Zhenhua
> >
> >
> > --
> > ___
> > 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] Yocto rootfs to support auto-login or remove the login prompt

[Zhenhua Luo]

Hi,

I want to generate a rootfs image which can skip the Linux login prompt or 
auto-login Linux? Is it possible in Yocto? If yes, may I know how to implement 
it?


Best Regards,

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

Re: [yocto] Can't replace login.defs with shadow-sysroot bbappend

[Zhenhua Luo]

Hi Oliver, 

The following line in shadow-sysroot.bb disables the final binary packages 
generation. You can try to add bbappend for shadow to do the customization. 

# don't create any packages
# otherwise: dbus-dev depends on shadow-sysroot-dev which depends on 
shadow-sysroot
# and this has another copy of /etc/login.defs already provided by shadow
PACKAGES = ""


Best Regards,

Zhenhua

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Oliver Graute
> Sent: Thursday, July 28, 2016 3:26 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] Can't replace login.defs with shadow-sysroot bbappend
> 
> Hello list,
> 
> i'm trying to replace /etc/login.defs on the target with my own one. So I
> created a shadow-sysroot_%.bbappend file with this content:
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"
> 
> # As we're overriding login.defs_shadow-sysroot we have to readd the
> checksum for it here # as it's containing the license for this component
> LIC_FILES_CHKSUM = "file://login.defs_shadow-
> sysroot;md5=286ba0946b3b8a300da3893d7b3af060"
> 
> SRC_URI_append = " file://login.defs_shadow-sysroot "
> 
> S = "${WORKDIR}"
> 
> do_install_append() {
>   install -d ${D}${sysconfdir}
>   install -p -m 755 ${S}/login.defs_shadow-sysroot
> ${D}${sysconfdir}/login.defs }
> 
> FILES_${PN} = "${D}${sysconfdir}/login.defs"
> 
> 
> If I run "bitbake shadow-sysroot" everything seems fine. But on the target
> there is no package shadow-sysroot after a complete image build. Just these:
> 
> opkg list  | grep shadow
> shadow - 4.2.1-r0
> shadow-base - 4.2.1-r0
> shadow-securetty - 4.2.1-r3
> 
> If I explicit added shadow-sysroot to my fsl-image.bb where I put all my other
> packages for the target in I get this error.
> 
> bitbake fsl-image
> 
> Collected errors:
>  * opkg_prepare_url_for_install: Couldn't find anything to satisfy 'shadow-
> sysroot'.
> 
> ERROR: Function failed: do_rootfs
> 
> 
> Some clue what is wrong here? I'am on jethro yocto branch.
> 
> Best regards,
> 
> Oliver
> --
> ___
> 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] The kernel versions used by Yocto

[Zhenhua Luo]

Hi,

I want to understand the kernel version selection criteria of Yocto release, 
can somebody please help to comment on it? I recall that Yocto uses the LTSI 
kernel, may I know if this is still the case?


Best Regards,

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

[linux-yocto] The kernel versions used by Yocto

[Zhenhua Luo]

Hi,

I want to understand the kernel version selection criteria of Yocto release, 
can somebody please help to comment on it? I recall that Yocto uses the LTSI 
kernel, may I know if this is still the case?


Best Regards,

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

Re: [yocto] bitbake problem

[Zhenhua Luo]

You can do the following check.

1.   Find out the package which produces libvolk.so.0.0.0, I think it 
should be volk.

2.   Check if the binary package is generated, which includes those dynamic 
libraries. It is possible that those libraries are generated and not shipped in 
any package.

3.   Update the recipe of vold to fix above problems to ensure the share 
libraries are shipped in corresponding binary package and included in rootfs.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Yile Ku
Sent: Wednesday, July 13, 2016 3:50 AM
To: yocto@yoctoproject.org
Subject: [yocto] bitbake problem

Is there someone who can explain how yocto checks these dependencies?  I need 
to debug this issue.
Thanks ahead of time.
Y-

ERROR: Unable to install packages. Command 
'/opt/Freescale/QorIQ-SDK-V1.8-20150619-yocto/build_bae-c2e-v2/tmp/sysroots/x86_64-linux/usr/bin/smart
 
--data-dir=/opt/Freescale/QorIQ-SDK-V1.8-20150619-yocto/build_bae-c2e-v2/tmp/work/b4860qds_64b-fsl-linux/fsl-image-full/1.0-r0/rootfs/var/lib/smart
 install -y libgcc1@ppc64e6500 gcc@ppc64e6500 libgcc-s-dev@ppc64e6500 
run-postinsts@all usdpaa-apps-staticdev@b4860qds_64b ldd@ppc64e6500 
usdpaa-apps@b4860qds_64b packagegroup-core-ssh-openssh@all apptrk@ppc64e6500 
asf@b4860qds_64b udev-extraconf@ppc64e6500 pme-tools@ppc64e6500 
eth-config@ppc64e6500 openssh-sftp-server@ppc64e6500 mtd-utils@ppc64e6500 
kmod@ppc64e6500 usdpaa-staticdev@b4860qds_64b util-linux@ppc64e6500 
fm-ucode-image@ppc64e6500 dpa-offload-dev@b4860qds_64b 
mtd-utils-jffs2@ppc64e6500 e2fsprogs-tune2fs@ppc64e6500 
packagegroup-core-eclipse-debug@all libpixman-1-0@ppc64e6500 g++@ppc64e6500 
gcov@ppc64e6500 dosfstools@ppc64e6500 
libglib-2.0-0@ppc64e6500 
e2fsprogs-e2fsck@ppc64e6500 packagegroup-fsl-core@all 
packagegroup-fsl-extend@all packagegroup-core-boot@b4860qds_64b 
packagegroup-core-full-cmdline@all sysklogd@ppc64e6500 merge-files@ppc64e6500 
packagegroup-core-buildessential@all rcw-image@b4860qds_64b usdpaa@b4860qds_64b 
packagegroup-core-nfs-server@all hypervisor-partman@ppc64e6500 
ceetm@b4860qds_64b dpa-offload-staticdev@b4860qds_64b libc6-dev@ppc64e6500 
usdpaa-dev@b4860qds_64b e2fsprogs-mke2fs@ppc64e6500 libgcov-dev@ppc64e6500 
sysfsutils@ppc64e6500 qoriq-debug@b4860qds_64b mtd-utils-ubifs@ppc64e6500 
kernel-image-3.12.37-rt51-qoriq-sdk-v1.8+gf488de6@b4860qds_64b
 bash@ppc64e6500 gnuradio@ppc64e6500 libelf1@ppc64e6500 dtc@ppc64e6500 
gdbserver@ppc64e6500 packagegroup-core-tools-debug@b4860qds_64b 
hyperrelay@ppc64e6500 tcf-qoriqdbg@ppc64e6500 sysstat@ppc64e6500 
fmc@b4860qds_64b e2fsprogs@ppc64e6500 net-tools@ppc64e6500 cpp@ppc64e6500 
eglibc-utils@ppc64e6500 kernel-devicetree@b4860qds_64b binutils@ppc64e6500 
u-boot-qoriq-images@b4860qds_64b libgcc1@lib32_ppce6500 gcc@lib32_ppce6500 
libgcov-dev@lib32_ppce6500 libgcc-s-dev@lib32_ppce6500 g++@lib32_ppce6500 
binutils@lib32_ppce6500 ldd@lib32_ppce6500 gcov@lib32_ppce6500 
cpp@lib32_ppce6500 eglibc-utils@lib32_ppce6500 eglibc-dev@lib32_ppce6500' 
returned 1:
Loading cache...
Updating cache...    [100%]

Computing transaction...error: Can't install 
gnuradio-3.7.5-r0@ppc64e6500: no package 
provides libvolk.so.0.0.0()(64bit)


ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/opt/Freescale/QorIQ-SDK-V1.8-20150619-yocto/build_bae-c2e-v2/tmp/work/b4860qds_64b-fsl-linux/fsl-image-full/1.0-r0/temp/log.do_rootfs.20153
ERROR: Task 7 
(/opt/Freescale/QorIQ-SDK-V1.8-20150619-yocto/meta-fsl-networking/images/fsl-image-full.bb,
 do_rootfs) failed with exit code '1'
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] customizing system configuration files in my image

[Zhenhua Luo]

Usually I do it by adding bbappend of corresponding packages to override 
original files, the interfaces is provided by init-ifupdown, the inittab is 
provided by sysvinit-inittab.

An example: 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/recipes-core/init-ifupdown


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ottavio Campana
Sent: Friday, July 01, 2016 5:12 PM
To: yocto@yoctoproject.org
Subject: [yocto] customizing system configuration files in my image

Hello,

I would like to customize an image I am developing based on core image minimal.

Particularly, I'd like to customize the files /etc/network/interfaces and 
/etc/inittab .

What should I do achieve that?

Thank you

Ottavio

--
[Videotec Logo]

Ottavio Campana
Product Manager - Electronic R Department

Office +39.0445.697.411  Fax +39.0445.697.414
Address  VIDEOTEC S.p.A. - Via Friuli, 6 - 36015 Schio (Vicenza) - Italy


Any information herein transmitted only concerns the person or the company 
named in the address and is deemed to be confidential It is strictly forbidden 
to transmit, post, forward or otherwise use said information to anyone other 
than the recipient. If you have received this message by mistake, please 
contact the sender and delete any relevant information from your computer. This 
mailbox is only meant for sending and receiving messages pertaining business 
matters and any other use for personal purposes is forbidden and unauthorized. 
Therefore, any email sent and received will be handled as ordinary business 
messages and subject to the company's own rules, and may thus be read also by 
people other than the user named in the mailbox address.

[Twitter Logo blue]   [Youtube logo red] 
[Linkedin logo blue] 




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

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Zhenhua Luo]

Thanks a lot for your comments, Daniel. 

Can somebody please shed light on how to fix the issue in Yocto recipes?  


Best Regards,

Zhenhua

> -Original Message-
> From: Daniel. [mailto:danielhi...@gmail.com]
> Sent: Friday, July 01, 2016 4:48 AM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
> 
> The problem is that ccache is not finding the compiler after environment-
> setup*.sh is sourced.Your error message can be foud at:
> https://github.com/ccache/ccache/blob/master/ccache.c#L2075. It seems that
> its searching for "gcc" when I though that kernel would search for
> "${CROSS_COMPILE}gcc"
> 
> 2016-06-29 22:54 GMT-03:00 Zhenhua Luo <zhenhua@nxp.com>:
> > I think you mean /usr/lib64/ccache/gcc instead of /usr/lib64/gcc, it is a 
> > valid
> link.
> >
> > $ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-
> linux
> > $ which gcc
> > /usr/lib64/ccache/gcc
> > $
> > $ ls -l /usr/lib64/ccache/gcc
> > lrwxrwxrwx 1 root root 16 Jun 29 18:22 /usr/lib64/ccache/gcc ->
> > ../../bin/ccache $ ls -l /usr/bin/ccache -rwxr-xr-x 1 root root 128584
> > Jan 26 14:58 /usr/bin/ccache $
> >
> >
> > Best Regards,
> >
> > Zhenhua
> >
> >> -Original Message-
> >> From: Daniel. [mailto:danielhi...@gmail.com]
> >> Sent: Wednesday, June 29, 2016 8:14 PM
> >> To: Zhenhua Luo <zhenhua@nxp.com>
> >> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> >> Subject: Re: [yocto] Failed to cross compile kernel with Yocto
> >> toolchain
> >>
> >> Is /usr/lib64/gcc a file or a link? Is it a valid link?
> >>
> >> 2016-06-29 5:52 GMT-03:00 Zhenhua Luo <zhenhua@nxp.com>:
> >> > The /usr/lib64/ccache is added in PATH by /etc/profile.d/ccache.sh
> >> > when ccache is installed on Fedora host, the issue disappears if
> >> > one of the following changes is done.
> >> >
> >> > 1.   Remove /usr/lib64/ccache from PATH
> >> >
> >> > 2.   Move /usr/lib64/ccache after /usr/bin in PATH
> >> >
> >> > 3.   Set CCACHE_PATH equals to PATH
> >> >
> >> > 4.   Unset CCACHE_PATH
> >> >
> >> >
> >> >
> >> > Another observation, before sourcing
> >> > environment-setup--poky-linux,
> >> > gcc can be found even if /usr/lib64/ccache is in prepend to PATH,
> >> > but after sourcing the environment-setup--poky-linux script,
> >> > the gcc can’t be found, this should be a bug of the
> >> > environment-setup--poky-linux
> >> > script. Should I open a Bugzilla ticket to track it?
> >> >
> >> >
> >> >
> >> > $ echo $PATH
> >> >
> >> > /usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/us
> >> > r/l
> >> > ocal/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home/bjsimics/bin
> >> >
> >> > which gcc
> >> >
> >> > /usr/lib64/ccache/gcc
> >> >
> >> > $ gcc -v
> >> >
> >> > Using built-in specs.
> >> >
> >> > COLLECT_GCC=/usr/bin/gcc
> >> >
> >> > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.3.1/lto-
> >> wra
> >> > pper
> >> >
> >> > Target: x86_64-redhat-linux
> >> >
> >> > Configured with: ../configure --enable-bootstrap
> >> > --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto
> >> > --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
> >> > --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
> >> > --enable-threads=posix --enable-checking=release --enable-multilib
> >> > --with-system-zlib --enable-__cxa_atexit
> >> > --disable-libunwind-exceptions --enable-gnu-unique-object
> >> > --enable-linker-build-id --with-linker-hash-style=gnu
> >> > --enable-plugin --enable-initfini-array --disable-libgcj
> >> > --with-default-libstdcxx-abi=gcc4-compatible --with-isl
> >> > --enable-libmpx --enable-gnu-indirect-function --with-tune=generic
> >> > --with-arch_32=i686 --build=x86_64-redhat-linux
> >> >
> >> > Thread model: posix
> >> >
> >> > gcc version 5.3.1 20160406 (Red Hat 5.3.

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Zhenhua Luo]

I think you mean /usr/lib64/ccache/gcc instead of /usr/lib64/gcc, it is a valid 
link. 

$ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-linux 
$ which gcc
/usr/lib64/ccache/gcc
$ 
$ ls -l /usr/lib64/ccache/gcc
lrwxrwxrwx 1 root root 16 Jun 29 18:22 /usr/lib64/ccache/gcc -> ../../bin/ccache
$ ls -l /usr/bin/ccache 
-rwxr-xr-x 1 root root 128584 Jan 26 14:58 /usr/bin/ccache
$ 


Best Regards,

Zhenhua

> -Original Message-
> From: Daniel. [mailto:danielhi...@gmail.com]
> Sent: Wednesday, June 29, 2016 8:14 PM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
> 
> Is /usr/lib64/gcc a file or a link? Is it a valid link?
> 
> 2016-06-29 5:52 GMT-03:00 Zhenhua Luo <zhenhua@nxp.com>:
> > The /usr/lib64/ccache is added in PATH by /etc/profile.d/ccache.sh
> > when ccache is installed on Fedora host, the issue disappears if one
> > of the following changes is done.
> >
> > 1.   Remove /usr/lib64/ccache from PATH
> >
> > 2.   Move /usr/lib64/ccache after /usr/bin in PATH
> >
> > 3.   Set CCACHE_PATH equals to PATH
> >
> > 4.   Unset CCACHE_PATH
> >
> >
> >
> > Another observation, before sourcing
> > environment-setup--poky-linux,
> > gcc can be found even if /usr/lib64/ccache is in prepend to PATH, but
> > after sourcing the environment-setup--poky-linux script, the gcc
> > can’t be found, this should be a bug of the
> > environment-setup--poky-linux
> > script. Should I open a Bugzilla ticket to track it?
> >
> >
> >
> > $ echo $PATH
> >
> > /usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/usr/l
> > ocal/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home/bjsimics/bin
> >
> > which gcc
> >
> > /usr/lib64/ccache/gcc
> >
> > $ gcc -v
> >
> > Using built-in specs.
> >
> > COLLECT_GCC=/usr/bin/gcc
> >
> > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.3.1/lto-
> wra
> > pper
> >
> > Target: x86_64-redhat-linux
> >
> > Configured with: ../configure --enable-bootstrap
> > --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr
> > --mandir=/usr/share/man --infodir=/usr/share/info
> > --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
> > --enable-threads=posix --enable-checking=release --enable-multilib
> > --with-system-zlib --enable-__cxa_atexit
> > --disable-libunwind-exceptions --enable-gnu-unique-object
> > --enable-linker-build-id --with-linker-hash-style=gnu --enable-plugin
> > --enable-initfini-array --disable-libgcj
> > --with-default-libstdcxx-abi=gcc4-compatible --with-isl
> > --enable-libmpx --enable-gnu-indirect-function --with-tune=generic
> > --with-arch_32=i686 --build=x86_64-redhat-linux
> >
> > Thread model: posix
> >
> > gcc version 5.3.1 20160406 (Red Hat 5.3.1-6) (GCC)
> >
> > $
> >
> > $ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-
> linux
> >
> > $
> >
> > $ echo $PATH
> >
> > /opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky
> > /2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/sbin:/opt/poky/2.1+sna
> > pshot/sysroots/x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroot
> > s/x86_64-pokysdk-linux/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pok
> > ysdk-linux/usr/bin/../x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/
> > sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux:/opt/poky/2.1
> > +snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-ucl
> > ibc:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/power
> > pc-poky-linux-musl:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/
> > bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home
> > /bjsimics/bin
> >
> > $
> >
> > $ which gcc
> >
> > /usr/lib64/ccache/gcc
> >
> > $ gcc -v
> >
> > ccache: error: Could not find compiler "gcc" in PATH
> >
> > $
> >
> >
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Zhenhua
> >
> >
> >
> > From: Khem Raj [mailto:raj.k...@gmail.com]
> > Sent: Tuesday, June 28, 2016 10:48 PM
> > To: Zhenhua Luo <zhenhua@nxp.com>
> > Cc: yocto@yoctoproject.org
> > Subject: RE: [yocto] Failed to cross compile kernel with Yocto
> > toolchain
> >
> >
> >
> > /usr/lib6

Re: [yocto] some questions about PPC yocto reference board mpc8315e-rdb

[Zhenhua Luo]

Hello rday, 

The error logs indicate that the default boot option(bootcmd=run sataboot) 
finds rootfs in /dev/sda1, but seems like the disk drive is not available or 
enabled on your board. 

To check whether kernel can boot up, you can try ramboot(ramboot=set bootargs 
root=/dev/ram rw console=ttyS0,115200; bootm fe50 fe10 fe70"). 
=> run ramboot 


Best Regards,

Zhenhua


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
> Sent: Wednesday, June 29, 2016 2:06 AM
> To: Yocto discussion list 
> Subject: [yocto] some questions about PPC yocto reference board mpc8315e-
> rdb
> 
> 
>   i'm currently working on a project involving some aging PPC boards 
> (including
> MPC8360), and i just happened across a MPC8315E-RDB (apparently unused),
> which could be useful since it's the PPC yocto reference board, which means i
> should be able to build fully working images for it without a great deal of 
> fuss.
> but first ...
> 
>   i'm *reasonably* confident that this system is in the state it was in as it 
> came
> from the factory, so i'm curious as to what it should be able to do without 
> any
> tweaking. ergo, plugged it in, attached a serial console, powered it up and 
> ...
> 
> U-Boot 1.3.0-rc2 (Mar 21 2008 - 16:00:02) MPC83XX
> 
> Reset Status:
> 
> CPU:   e300c3, Rev: Unknown revision number:80b40011
> Warning: Unsupported cpu revision!
> Board: Freescale MPC8315ERDB Rev 1.0
> I2C:   ready
> DRAM:  128 MB
> PCIE0: No link
> PCIE1: No link
> FLASH:  8 MB
> NAND:  32 MiB
> In:serial
> Out:   serial
> Err:   serial
> Net:   eTSEC0, eTSEC1
> Hit any key to stop autoboot:  0
> 
>   whew, that is some kind of old. and here are the current variables (again, i
> have no idea if these were changed since the factory):
> 
> => print
> nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
>   ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
>   console=$consoledev,$baudrate $othbootargs;tftp $loadaddr
>   $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
> bootdelay=6
> baudrate=115200
> loads_echo=1
> ethaddr=04:00:00:00:00:0A
> eth1addr=04:00:00:00:00:0B
> loadaddr=20
> netdev=eth0
> consoledev=ttyS0
> ramdiskaddr=100
> ramdiskfile=ramfs.83xx
> fdtaddr=40
> fdtfile=mpc8315erdb.dtb
> ethact=eTSEC0
> mtdids=nor0=nor,nand0=nand
> sataboot=set bootargs root=/dev/sda1 rw console=ttyS0,115200; bootm
> fe50 - fe70 bootcmd=run sataboot smbboot=set bootargs
> root=/dev/ram rw console=ttyS0,115200 ramdisk_size=78800; tftp
> $ramdiskaddr $smbfs; bootm fe50 $ramdiskaddr fe70 ramboot=set
> bootargs root=/dev/ram rw console=ttyS0,115200; bootm fe50 fe10
> fe70 jffs2boot=set bootargs root=/dev/mtdblock1 rootfstype=jffs2 rw
> console=ttyS0,115200; bootm fe50 - fe70
> ipaddr=10.196.31.57
> serverip=10.196.31.38
> bootargs=root=/dev/ram rw console=ttyS0,115200 ramdisk_size=50
> stdin=serial stdout=serial stderr=serial
> 
> Environment size: 1117/8188 bytes
> =>
> 
>   so let's see what happens if i just let it boot:
> 
> 
> Hit any key to stop autoboot:  0
> ## Booting image at fe50 ...
>Image Name:   Linux-2.6.23
>Created:  2008-03-21   6:25:53 UTC
>Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>Data Size:1722476 Bytes =  1.6 MB
>Load Address: 
>Entry Point:  
>Verifying Checksum ... OK
>Uncompressing Kernel Image ... OK
>Booting using the fdt at 0xfe70
>Loading Device Tree to 007fc000, end 007fefff ... OK Using MPC8315 RDB
> machine description Linux version 2.6.23 (yhh@rock) (gcc version 4.1.2) #1 Fri
> Mar 21 14:25:50 CST 2008 console [udbg0] enabled
> setup_arch: bootmem
> mpc8315_rdb_setup_arch()
> Freescale SerDes at e00e3000 initialized Found MPC83xx PCI host bridge at
> 0x8500. Firmware bus number: 0->0 Found MPC83xx PCI host
> bridge at 0xe0009000. Firmware bus number: 0->0 Found MPC83xx
> PCI host bridge at 0xe000a000. Firmware bus number: 0->0
> arch: exit
> Zone PFN ranges:
>   DMA 0 ->32768
>   Normal  32768 ->32768
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0:0 ->32768
> Built 1 zonelists in Zone order.  Total pages: 32512 Kernel command line:
> root=/dev/sda1 rw console=ttyS0,115200 IPIC (128 IRQ sources) at faef7700 PID
> hash table entries: 512 (order: 9, 2048 bytes) Dentry cache hash table 
> entries:
> 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3,
> 32768 bytes)
> Memory: 126064k/131072k available (3380k kernel code, 4864k reserved, 148k
> data, 100k bss, 164k init) Mount-cache hash table entries: 512
> NET: Registered protocol family 16
> CI: Probing PCI hardware
> Generic PHY: Registered new driver
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Zhenhua Luo]

The /usr/lib64/ccache is added in PATH by /etc/profile.d/ccache.sh when ccache 
is installed on Fedora host, the issue disappears if one of the following 
changes is done.

1.   Remove /usr/lib64/ccache from PATH

2.   Move /usr/lib64/ccache after /usr/bin in PATH

3.   Set CCACHE_PATH equals to PATH

4.   Unset CCACHE_PATH

Another observation, before sourcing environment-setup--poky-linux, gcc 
can be found even if /usr/lib64/ccache is in prepend to PATH, but after 
sourcing the environment-setup--poky-linux script, the gcc can’t be 
found, this should be a bug of the environment-setup--poky-linux script. 
Should I open a Bugzilla ticket to track it?

$ echo $PATH
/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home/bjsimics/bin
which gcc
/usr/lib64/ccache/gcc
$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.3.1/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap 
--enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr 
--mandir=/usr/share/man --infodir=/usr/share/info 
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared 
--enable-threads=posix --enable-checking=release --enable-multilib 
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions 
--enable-gnu-unique-object --enable-linker-build-id 
--with-linker-hash-style=gnu --enable-plugin --enable-initfini-array 
--disable-libgcj --with-default-libstdcxx-abi=gcc4-compatible --with-isl 
--enable-libmpx --enable-gnu-indirect-function --with-tune=generic 
--with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 5.3.1 20160406 (Red Hat 5.3.1-6) (GCC)
$
$ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-linux
$
$ echo $PATH
/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/../x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-uclibc:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-musl:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home/bjsimics/bin
$
$ which gcc
/usr/lib64/ccache/gcc
$ gcc -v
ccache: error: Could not find compiler "gcc" in PATH
$


Best Regards,

Zhenhua

From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Tuesday, June 28, 2016 10:48 PM
To: Zhenhua Luo <zhenhua@nxp.com>
Cc: yocto@yoctoproject.org
Subject: RE: [yocto] Failed to cross compile kernel with Yocto toolchain


/usr/lib64/ccache is unusual why do you have it in path and if you really need 
it add it after all other paths. Check your env first

On Jun 27, 2016 10:56 PM, "Zhenhua Luo" 
<zhenhua@nxp.com<mailto:zhenhua@nxp.com>> wrote:
Hello Khem,

> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com<mailto:raj.k...@gmail.com>]
> Sent: Tuesday, June 28, 2016 12:36 AM
> To: Zhenhua Luo <zhenhua@nxp.com<mailto:zhenhua@nxp.com>>
> Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> On Mon, Jun 27, 2016 at 1:16 AM, Zhenhua Luo 
> <zhenhua@nxp.com<mailto:zhenhua@nxp.com>>
> wrote:
> > Hello all,
> >
> >
> >
> > I generate the Yocto toolchain by “bitbake meta-toolchain”, and use
> > this toolchain to cross-compile kernel, I met the following error. Is
> > this a bug or I missed something? My host Linux is Fedora 22.
>
> its better to start using bitbake -cpopulate_sdk  to generate
> SDKs.
>
>
> >
> >
> >
> > $ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-
> linux
> >
> > $ cd linux/
> >
> > $ make corenet32_smp_defconfig
> >
> >   HOSTCC  scripts/kconfig/conf.o
> >
> > ccache: error: Could not find compiler "gcc" in PATH
>
> did you see if gcc is in your path after sourcing SDK env script?
[Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script. but 
the /usr/bin is in the PATH env variable.
$ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-linux
$ echo $PATH
/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/sbin:/opt/poky/2.1+snapshot/sys

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Zhenhua Luo]

Hi, 

> From: Burton, Ross [mailto:ross.bur...@intel.com] 
> Sent: Tuesday, June 28, 2016 6:27 PM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: Khem Raj <raj.k...@gmail.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
>
> On 28 June 2016 at 06:56, Zhenhua Luo <zhenhua@nxp.com> wrote:
> Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script. but 
> the /usr/bin is in the PATH env variable.
> 
> You *do* have a gcc in /usr/bin, right?
[Zhenhua Liuo] Right. 


Best Regards,

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

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

[Zhenhua Luo]

Hello Khem, 

> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Tuesday, June 28, 2016 12:36 AM
> To: Zhenhua Luo <zhenhua@nxp.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Failed to cross compile kernel with Yocto toolchain
> 
> On Mon, Jun 27, 2016 at 1:16 AM, Zhenhua Luo <zhenhua@nxp.com>
> wrote:
> > Hello all,
> >
> >
> >
> > I generate the Yocto toolchain by “bitbake meta-toolchain”, and use
> > this toolchain to cross-compile kernel, I met the following error. Is
> > this a bug or I missed something? My host Linux is Fedora 22.
> 
> its better to start using bitbake -cpopulate_sdk  to generate
> SDKs.
> 
> 
> >
> >
> >
> > $ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-
> linux
> >
> > $ cd linux/
> >
> > $ make corenet32_smp_defconfig
> >
> >   HOSTCC  scripts/kconfig/conf.o
> >
> > ccache: error: Could not find compiler "gcc" in PATH
> 
> did you see if gcc is in your path after sourcing SDK env script? 
[Luo Zhenhua-B19537] gcc can't be found after sourcing the SDK env script. but 
the /usr/bin is in the PATH env variable. 
$ source /opt/poky/2.1+snapshot/environment-setup-ppce500mc-poky-linux
$ echo $PATH
/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/sbin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/../x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-uclibc:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-musl:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bjsimics/.local/bin:/home/bjsimics/bin
$ echo $CCACHE_PATH
/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/../x86_64-pokysdk-linux/bin:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-uclibc:/opt/poky/2.1+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/powerpc-poky-linux-musl:
$ which gcc
/usr/lib64/ccache/gcc
$ gcc -v
ccache: error: Could not find compiler "gcc" in PATH


Best Regards, 

Zhenhua
  
> > scripts/Makefile.host:108: recipe for target 'scripts/kconfig/conf.o'
> > failed
> >
> > make[1]: *** [scripts/kconfig/conf.o] Error 1
> >
> > Makefile:541: recipe for target 'corenet32_smp_defconfig' failed
> >
> > make: *** [corenet32_smp_defconfig] Error 2
> >
> >
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Zhenhua
> >
> >
> > --
> > ___
> > 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] The linux login prompt delays about 5 seconds with systemd rootfs

[Zhenhua Luo]

Hello all,

I try to add the following lines in local.conf to enable systemd, the 
core-image-minimal rootfs can be built successfully.
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""

When the systemd rootfs is used to bootup the board,  After the last systemd 
service startup log is printed, the console will wait about 5 seconds before 
the linux login prompt appears.
[  OK  ] Started D-Bus System Message Bus.
 Starting Login Service...
[  OK  ] Started Login Service.

Poky (Yocto Project Reference Distro) 2.1+snapshot-20160616 t1040d4rdb ttyS0

t1040d4rdb login:

Does somebody know if the delay time can be customized and how to set it?


Best Regards,

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

Re: [yocto] The build issue of ext2.gz and ext2.gz.u-boot rootfs

[Zhenhua Luo]

I have submitted a patch, please review.

http://patchwork.openembedded.org/patch/124761/.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Zhenhua Luo
Sent: Monday, June 13, 2016 5:53 PM
To: yocto@yoctoproject.org
Subject: [yocto] The build issue of ext2.gz and ext2.gz.u-boot rootfs

Hi all,

I try to use the master branch of poky to build ext2.gz and ext2.gz.u-boot 
rootfs at the same time, the following error will appear. The same issue can be 
reproduced for other machines as well.
[...snip...]
| Image Name:   core-image-minimal-b4860qds-2016
| Created:  Sun Jun 12 23:18:26 2016
| Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
| Data Size:50613518 Bytes = 49427.26 kB = 48.27 MB
| Load Address: 
| Entry Point:  
| mkimage: Can't open 
/home/yocto/poky/b4860qds/tmp/deploy/images/b4860qds/core-image-minimal-b4860qds-20160613041724.rootfs.ext2.gz:
 No such file or directory

The following is the definition of do_image_ext2, the ext2.gz file is cleaned 
by the first "oe_mkimage  ... gzip clean" before the second oe_mkimage 
execution.
do_image_ext2() {
oe_mkext234fs ext2 -i 4096
cd /home/yocto/poky/b4860qds/tmp/deploy/images/b4860qds
gzip -f -9 -c 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2 > 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz
gzip -f -9 -c 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2 > 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz; oe_mkimage 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz gzip clean
oe_mkimage 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz none
rm core-image-minimal-b4860qds-20160613042048.rootfs.ext2
}

If change[1] is made for poky/meta/classes/image.bbclass, the isuse can be 
reproduced every time, if change[2] is made for 
poky/meta/classes/image.bbclass, the isuse can't be reproduced. Without change, 
the sequence of ctypes is random, accordingly the build issue apprears randomly.
Change[1]:
-ctypes = set(d.getVar('COMPRESSIONTYPES', True).split())
+ctypes = sorted(set(d.getVar('COMPRESSIONTYPES', True).split()))
Change[2]:
-ctypes = set(d.getVar('COMPRESSIONTYPES', True).split())
+ctypes = sorted(set(d.getVar('COMPRESSIONTYPES', True).split()), 
reverse=True)

I meet either the following two issues when I only build ext2.gz.u-boot,  the 
following is the error.
Taskhash mismatch issue:
ERROR: core-image-minimal-1.0-r0 do_image_ext2: Taskhash mismatch 
bb5f9a754f83ef6534d62ca5ea64d631 verses c56d6505b35344945430e1d6cae3867c for 
/home/yocto/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_ext2
ERROR: Taskhash mismatch bb5f9a754f83ef6534d62ca5ea64d631 verses 
c56d6505b35344945430e1d6cae3867c for 
/home/yocto/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_ext2
Ext2.gz remove issue:
| rm: cannot remove 
'core-image-minimal-b4860qds-20160613044631.rootfs.ext2.gz': No such file or 
directory

Any suggestion of how to fix such issues?


Best Regards,

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

[yocto] The build issue of ext2.gz and ext2.gz.u-boot rootfs

[Zhenhua Luo]

Hi all,

I try to use the master branch of poky to build ext2.gz and ext2.gz.u-boot 
rootfs at the same time, the following error will appear. The same issue can be 
reproduced for other machines as well.
[...snip...]
| Image Name:   core-image-minimal-b4860qds-2016
| Created:  Sun Jun 12 23:18:26 2016
| Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
| Data Size:50613518 Bytes = 49427.26 kB = 48.27 MB
| Load Address: 
| Entry Point:  
| mkimage: Can't open 
/home/yocto/poky/b4860qds/tmp/deploy/images/b4860qds/core-image-minimal-b4860qds-20160613041724.rootfs.ext2.gz:
 No such file or directory

The following is the definition of do_image_ext2, the ext2.gz file is cleaned 
by the first "oe_mkimage  ... gzip clean" before the second oe_mkimage 
execution.
do_image_ext2() {
oe_mkext234fs ext2 -i 4096
cd /home/yocto/poky/b4860qds/tmp/deploy/images/b4860qds
gzip -f -9 -c 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2 > 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz
gzip -f -9 -c 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2 > 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz; oe_mkimage 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz gzip clean
oe_mkimage 
core-image-minimal-b4860qds-20160613042048.rootfs.ext2.gz none
rm core-image-minimal-b4860qds-20160613042048.rootfs.ext2
}

If change[1] is made for poky/meta/classes/image.bbclass, the isuse can be 
reproduced every time, if change[2] is made for 
poky/meta/classes/image.bbclass, the isuse can't be reproduced. Without change, 
the sequence of ctypes is random, accordingly the build issue apprears randomly.
Change[1]:
-ctypes = set(d.getVar('COMPRESSIONTYPES', True).split())
+ctypes = sorted(set(d.getVar('COMPRESSIONTYPES', True).split()))
Change[2]:
-ctypes = set(d.getVar('COMPRESSIONTYPES', True).split())
+ctypes = sorted(set(d.getVar('COMPRESSIONTYPES', True).split()), 
reverse=True)

I meet either the following two issues when I only build ext2.gz.u-boot,  the 
following is the error.
Taskhash mismatch issue:
ERROR: core-image-minimal-1.0-r0 do_image_ext2: Taskhash mismatch 
bb5f9a754f83ef6534d62ca5ea64d631 verses c56d6505b35344945430e1d6cae3867c for 
/home/yocto/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_ext2
ERROR: Taskhash mismatch bb5f9a754f83ef6534d62ca5ea64d631 verses 
c56d6505b35344945430e1d6cae3867c for 
/home/yocto/poky/meta/recipes-core/images/core-image-minimal.bb.do_image_ext2
Ext2.gz remove issue:
| rm: cannot remove 
'core-image-minimal-b4860qds-20160613044631.rootfs.ext2.gz': No such file or 
directory

Any suggestion of how to fix such issues?


Best Regards,

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

Re: [yocto] [Fwd: gobject introspection release notes]

[Zhenhua Luo]

Hello Chris,

Please see my inline comments.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Chris Trobridge
Sent: Monday, April 25, 2016 11:01 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] [Fwd: gobject introspection release notes]

Any ideas as to why "qemu-ppc64 crashes out immediately"?

I can confirm the build ends in a segfault when I tried building 
gobject-introspection for the t1042d4rdb-64b machine.
[Luo Zhenhua-B19537] This is a gobject-introspection support issue of QEMU 
PPC64, the fix is not available now, you can use the following workaround to 
bypass the issue.
http://git.yoctoproject.org/cgit.cgi/meta-fsl-ppc/tree/README#n18

I did get one qemu crash recorded by Fedora but the actual crash dumps 
(appended) are for a PowerPC.  That said, given the dump, either the processor 
got nowhere or they are likely corrupt.  The invalid access reported is roughly 
to the stack but with the upper 32-bits zeroed.

If I configure bitbake for a 32-bit build (t1042d4rdb) then the build fails 
with  "Unable to find CPU definition" (cpu e5500) so a 32-bit build is out of 
the question too.

The command line from the wrapper is:
PSEUDO_UNLOAD=1 qemu-ppc -r 2.6.32  -cpu e5500 -L 
/home/chris/yocto/build/tmp/sysroots/t1042d4rdb -E 
LD_LIBRARY_PATH=$GIR_EXTRA_LIBS_PATH:.libs:/home/chris/yocto/build/tmp/sysroots/t1042d4rdb//usr/lib:/home/chris/yocto/build/tmp/sysroots/t1042d4rdb//lib
  "$@"
[Luo Zhenhua-B19537] Please fetch the latest commit, the issue is fixed by 
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=krogoth=27e202f2d9114a64b67c83eb7eafeb12de5ceea7.

The cpu is supported by the fedora qemu-ppc64, but not qemu-ppc - ie it's a 
64-bit processor that's not supported in 32-bit mode.

This is not massively urgent for me but it may be important in the future and I 
am curious as to whether the problem is in the qemu emulation or in the 
emulated code.

Regards,
Chris
| Invalid data memory access: 0x007fe8f0
| NIP 0040008046c8   LR  CTR  XER 
 CPU#0
| MSR 80006000 HID0   HF 6000 idx 0
| TB 00025634 110100571322161
| GPR00  0040007fe970 004000848e00 0040007fe970
| GPR04    
| GPR08    
| GPR12    
| GPR16    
| GPR20    
| GPR24    
| GPR28    
| CR   [ -  -  -  -  -  -  -  -  ] RES 
| FPR00    
| FPR04    
| FPR08    
| FPR12    
| FPR16    
| FPR20    
| FPR24    
| FPR28    
| FPSCR 
| Invalid segfault errno (4200)
| NIP 0040008046c8   LR  CTR  XER 
 CPU#0
| MSR 80006000 HID0   HF 6000 idx 0
| TB 00025634 110100578368626
| GPR00  0040007fe970 004000848e00 0040007fe970
| GPR04    
| GPR08    
| GPR12    
| GPR16    
| GPR20    
| GPR24    
| GPR28    
| CR   [ -  -  -  -  -  -  -  -  ] RES 
| FPR00    
| FPR04    
| FPR08    
| FPR12    
| FPR16    
| FPR20    
| FPR24    
| FPR28 

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

[Zhenhua Luo]

If the SHA exists in a tag instead of any branch, you can use nobranch 
parameter, refer to 
http://git.yoctoproject.org/cgit.cgi/poky/tree/bitbake/lib/bb/fetch2/git.py?id=c4bcaa3f7ceac346af1555fff2b526ceeac92a54#n47.
 


Best Regards,

Zhenhua

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Bruce Ashfield
> Sent: Tuesday, April 26, 2016 10:11 AM
> To: Jaggi, Manish ; Burton, Ross
> 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Fetcher failure: Unable to find revision
> 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> upstream
> 
> On 2016-04-25 9:05 PM, Jaggi, Manish wrote:
> >
> > 
> > From: Bruce Ashfield [bruce.ashfi...@windriver.com]
> > Sent: Monday, April 25, 2016 11:04 PM
> > To: Jaggi, Manish; Burton, Ross
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] Fetcher failure: Unable to find revision
> > 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> > upstream
> >
> > On 2016-04-25 12:10 PM, Jaggi, Manish wrote:
> >>
> >> -
> >> ---
> >> *From:* Burton, Ross 
> >> *Sent:* Monday, April 25, 2016 8:12 PM
> >> *To:* Jaggi, Manish
> >> *Cc:* yocto@yoctoproject.org
> >> *Subject:* Re: [yocto] Fetcher failure: Unable to find revision
> >> 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from
> >> upstream
> >>
> >> On 25 April 2016 at 14:30, Jaggi, Manish
> >>  >> > wrote:
> >>
> >>  It seems the revid / tag is not on any branch
> >>  git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
> >>  returns nothing.
> >>
> >>  How to fix this issue ?
> >>
> >>
> >> You probably want to use git branch -r --contains 213... as otherwise
> >> git branch will only list local branches.  The web UI says that this
> >> commit exists on master though...
> >>
> >> [Manish] Same output with -r.
> >> Can you please share the link of web ui. As per the error it is not
> >> on master branch.
> >
> > linux-yoct-dev and linux-yocto-4.4 are different trees.
> > linux-yocto-dev tracks the latest mainline kernel, not -stable.
> >
> > So if you are looking for 4.4.3 on linux-yocto-dev, you aren't going
> > to find it.
> >
> > [Manish] the 4.4.3 tag is also not on master branch of the 4.4 tree.
> > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.4/tag/?h=stand
> > ard/base=v4.4.3
> > The master is 4.4
> 
> It's on standard/base. master is left as the initial branch point of the 
> repository.
> When LTSI is available, I tend to update master, but since 4.4 has no LTSI
> content, I leave master alone.
> 
> Also note: I'm currently not pushing and -stable updates to that tree, since 
> I'm
> temporarily frozen for the yocto 2.1 release.
> 
> 
> >
> > A clone and check from tag works manually, but when bitbake fetches it, it
> throws error as bitbake is not able to find the commit on master branch.
> > How to fix thisk
> 
> don't use master, use standard/base as the branch.
> 
> Bruce
> 
> >
> > Bruce
> >
> >>
> >>
> >> Ross
> >>
> >>
> >
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Using Yocto with NXP QorIQ Processors

[Zhenhua Luo]

Hi Chris,

The QorIQ SDK uses recent Yocto version, e.g. the SDK 2.0  is based on Yocto 
2.0(Jethro).  When the SDK is formally released in Q2/2016, the SDK recipes 
will be upstreamed to master of community layers.

You can use either SDK ISOs available in NXP official 
website(www.nxp.com) or the BSP layers in Yocto website 
(http://git.yoctoproject.org/cgit.cgi/).

* QorIQ ARM targets: meta-fsl-arm

* QorIQ PPC targets: meta-fsl-ppc


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Chris Trobridge
Sent: Monday, April 18, 2016 9:58 PM
To: yocto@yoctoproject.org
Subject: [yocto] Using Yocto with NXP QorIQ Processors

Has anyone attempted to use the Qoriq BSP layers with them main Yocto release 
rather than the NXP (ex Freescale) SDK they come bundled in?

I ask because the NXP SDK is somewhat behind the main Yocto release schedule.

It should be easier to port the BSP to the current Yocto but I have no idea 
what issues I am likely to hit.

I will try this at some point when I have enough free time but for planning 
purposes I would interested in how anyone else has got on attempting this.

Are Qoriq users restricted to the official SDK or would they get third-party 
support?

Regards,
Chris

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

[yocto] Build failed for ext2.gz.u-boot rootfs

[Zhenhua Luo]

Hi,

I try to use master branch of poky to build ext2.gz.u-boot rootfs image for 
qemuarm target, the build failed as the following.  Does somebody know the 
reason and how to fix it? Thanks in advance.
| Image Name:   core-image-sato-sdk-qemuarm-2016
| Created:  Wed Mar  9 06:11:14 2016
| Image Type:   ARM Linux RAMDisk Image (gzip compressed)
| Data Size:445885242 Bytes = 435434.81 kB = 425.23 MB
| Load Address: 
| Entry Point:  
| mkimage: Write error on 
/home/yocto/poky/qemuarm/tmp/deploy/images/qemuarm/core-image-sato-sdk-qemuarm-20160309120517.rootfs.ext2.u-boot:
 Bad address
| WARNING: 
/home/yocto/poky/qemuarm/tmp/work/qemuarm-poky-linux-gnueabi/core-image-sato-sdk/1.0-r0/temp/run.do_image_ext2.4861:1
 exit 1 from 'mkimage -A arm -O linux -T ramdisk -C $2 -n 
core-image-sato-sdk-qemuarm-20160309120517 -d 
/home/yocto/poky/qemuarm/tmp/deploy/images/qemuarm/$1 
/home/yocto/poky/qemuarm/tmp/deploy/images/qemuarm/$1.u-boot'
| ERROR: Function failed: do_image_ext2 (log file is located at 
/home/yocto/poky/qemuarm/tmp/work/qemuarm-poky-linux-gnueabi/core-image-sato-sdk/1.0-r0/temp/log.do_image_ext2.4861)

Build Configuration:
BB_VERSION= "1.29.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "qemuarm"
DISTRO= "poky"
DISTRO_VERSION= "2.0+snapshot-20160309"
TUNE_FEATURES = "arm armv5 thumb dsp"
TARGET_FPU= "soft"
meta
meta-poky
meta-yocto-bsp= "master:5ac3dc76a5afc2ed35b1abfc8e330e0c580eadf0"


Best Regards,

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

Re: [yocto] extracting SDK for supporting both 32 and 64 bit applications

[Zhenhua Luo]

Hi Michael,

If you mean the standalone toolchain on host, the 32b and 64b build should be 
done by different toolchain, you need to install both 32b and 64b toolchain.

If you mean the rootfs on target board, you can select a 64b target and add 32b 
package in corresponding rootfs bb file, e.g. IMAGE_INSTALL_append = " 
lib32-zlib lib32-gcc ...'.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Michael Fainstein
Sent: Thursday, January 28, 2016 2:46 PM
To: yocto@yoctoproject.org
Subject: [yocto] extracting SDK for supporting both 32 and 64 bit applications

Dear community,

I am using Freescale's SDK 1.8 based on poky 1.6.2.

How can extract SDK that supports building of both 32 and 64 bit applications?

I defined configuration for my board to be 32 bit with 64 bit kernel and 
extracted SDK for application development.
Everything works fine: I can build 32 bit applications and execute them on my 
board and peek at PCI memory that is far above 32 bit memory limit.
I can build and load kernel loadable modules using bitbake.
However, building kernel modules using extracted SDK fails: while there are 64 
bit tools in bitbake environment, there are no 64 bit tools and 64 bit headers 
in extracted SDK environment.
I tried also to define my board as 64 bit with multilibs and added to my image 
32-bit libraries. However, in this configuration the extracted SDK didn't 
contain 32 bit tools and headers. How do I add both 32 and 64 bit tools and 
headers to native SDK?


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

[yocto] The problem of linux-yocto external source build

[Zhenhua Luo]

Hi all,

I try to use the HEAD of poky master to build the external source for 
linux-yocto. the following lines are added in conf/local.conf.
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
INHERIT += "externalsrc"
EXTERNALSRC_pn-linux-yocto = "/home/yocto/my-linux-src"

When I build a rootfs which includes cyptodev-module, the following error 
appears. Can somebody please help on how to fix the build error?
$ bitbake cryptodev-module
Loading cache: 100% 
|###|
 ETA:  00:00:00
Loaded 1296 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.28.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-22"
TARGET_SYS= "i586-poky-linux"
MACHINE   = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "2.0+snapshot-20160111"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:221d864042658daa054281aab439b44d54fe94d7"

NOTE: Preparing RunQueue
ERROR: Task do_make_scripts in 
/home/yocto/poky/meta/recipes-kernel/cryptodev/cryptodev-module_1.8.bb depends 
upon non-existent task do_shared_workdir in 
/home/yocto/poky/meta/recipes-kernel/linux/linux-yocto_4.1.bb

Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Best Regards,

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

[yocto] [meta-selinux][PATCH] Enable two options to ensure selinux can boot up

[Zhenhua Luo]

* CONFIG_SECURITY=y
* CONFIG_SECURITYFS=y

Signed-off-by: Zhenhua Luo zhenhua@freescale.com
---
 recipes-kernel/linux/linux-yocto/selinux.cfg | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-kernel/linux/linux-yocto/selinux.cfg 
b/recipes-kernel/linux/linux-yocto/selinux.cfg
index 53cdf57..2edd366 100644
--- a/recipes-kernel/linux/linux-yocto/selinux.cfg
+++ b/recipes-kernel/linux/linux-yocto/selinux.cfg
@@ -18,6 +18,8 @@ CONFIG_EXT4_FS_SECURITY=y
 CONFIG_JFS_SECURITY=y
 CONFIG_REISERFS_FS_SECURITY=y
 CONFIG_JFFS2_FS_SECURITY=y
+CONFIG_SECURITY=y
+CONFIG_SECURITYFS=y
 CONFIG_SECURITY_NETWORK=y
 CONFIG_SECURITY_SELINUX=y
 CONFIG_SECURITY_SELINUX_BOOTPARAM=y
-- 
1.9.3

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

Re: [yocto] Yocto branches policy for concurrent SDK releases

[Zhenhua Luo]

Please ignore, sorry for the noise. 


Best Regards,

Zhenhua

 -Original Message-
 From: Luo Zhenhua-B19537
 Sent: Friday, November 22, 2013 6:44 PM
 To: Software Development Power Arch Multicore
 Cc: yocto@yoctoproject.org
 Subject: [mcswdev] Yocto branches policy for concurrent SDK releases
 Importance: High
 
 Hi all,
 
 Currently concurrent SDKs are on-going(e.g. SDK 1.5, T1040/T2080, LS1,
 etc), the same Yocto branch is used for multiple releases, there is
 conflict of Yocto recipes for different SDKs.
 
 To resolve above issue, following branch mechanism will be used:
 
 1. For those layers without conflict(poky, meta-oe, meta-virtualization
 and layers reused from community), same branch will be used and no extra
 branches need to be created, change for those layer should be upstreamed
 synchronously.
 
 2. For those layers with conflict, the branch specific to SDK are created,
 currently meta-fsl-ppc and meta-fsl-networking have conflict for
 different SDKs. Following branches will co-exist for such layers.
a. Yocto release branch: dylan, dora. the common changes for all SDKs
 should be submitted against this branch and cherry-picked to SDK specific
 branches. The changes should be upstreamed synchronously.
b. SDK specific branch: dylan-sdk1.5, dylan-t1_t2, etc. The SDK
 specific change should be submitted against SDK branch, when SDK is
 formally released, the changes will be upstreamed.
 
 Please let me know if any comment.
 
 
 Best Regards,
 
 Zhenhua


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

Re: [yocto] [meta-cloud-services][PATCH] erlang: skip the host library path check to fix cross-compile issue

[Zhenhua Luo]

Bruce, thanks for your comments. V2 coming soon. 


Best Regards,

Zhenhua


 -Original Message-
 From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
 Sent: Tuesday, November 19, 2013 9:29 PM
 To: Luo Zhenhua-B19537; yocto@yoctoproject.org
 Cc: Liu Ting-B28495; Guo Chunrong-B40290; Yu Zongchun-B40527
 Subject: Re: [meta-cloud-services][PATCH] erlang: skip the host library
 path check to fix cross-compile issue
 
 Thanks for the patch!
 
 A couple of requests.
 
 Can you list the compile issue here ? i.e. just a bit of the error
 message showing it clearly. Someone else searching for a problem will
 find it very useful!
 
 On 13-11-19 05:27 AM, Zhenhua Luo wrote:
  Signed-off-by: Zhenhua Luo zhenhua@freescale.com
  ---
.../erlang/erlang-fix-build-issue-in-Yocto.patch   | 25
 ++
.../recipes-devtools/erlang/erlang_R15B.bb |  2 ++
2 files changed, 27 insertions(+)
create mode 100644
  meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-i
  n-Yocto.patch
 
  diff --git
  a/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue
  -in-Yocto.patch
  b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue
  -in-Yocto.patch
  new file mode 100644
  index 000..2d4b7b5
  --- /dev/null
  +++ b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-i
  +++ ssue-in-Yocto.patch
  @@ -0,0 +1,25 @@
  +Upstream-Status: Inappropriate [The fix is specific to Yocto build
  +env]
  +
  +Skip host library path check to fix following Yocto insane check issue:
  +ERROR: This autoconf log indicates errors, it looked at host include
 and/or library paths while determining system capabilities.
  +Rerun configure task after fixing this.
  +
  +Signed-off-by: Zhenhua Luo zhenhua@freescale.com
  +
  +--- otp_src_R15B/erts/configure.in.orig2011-12-14
 04:22:11.0 -0600
   otp_src_R15B/erts/configure.in 2013-11-19 04:15:33.694334610 -
 0600
  +@@ -1469,10 +1469,10 @@
  +   # ln -s libdlpi.so.1 $try_dlpi_lib/libdlpi.so
  +   ])
  +fi
  +-   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
  +-   unset -v try_dlpi_lib
  +-   AC_MSG_NOTICE([Extending the search to include /lib])
  +-   AC_CHECK_LIB(dlpi, dlpi_open)
  ++#   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
  ++#   unset -v try_dlpi_lib
  ++#   AC_MSG_NOTICE([Extending the search to include /lib])
  ++#   AC_CHECK_LIB(dlpi, dlpi_open)
  +if test x$ac_cv_lib_dlpi_dlpi_open = xno; then
  +   LDFLAGS=$save_ldflags
  +fi
  diff --git a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  index 68d144b..8d8e28b 100644
  --- a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  +++ b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  @@ -9,6 +9,7 @@ EXTRA_OEMAKE = BUILD_CC='${BUILD_CC}'
 
EXTRA_OECONF = --with-ssl=${STAGING_DIR_HOST}${layout_exec_prefix}
 
  +EXTRA_OECONF_append_powerpc =  --disable-smp-support --disable-hipe
 
 This should be a separate patch. Can you split the commit and send this
 as a two part series ?
 
 Bruce
 
EXTRA_OECONF_append_arm =  --disable-smp-support --disable-hipe
EXTRA_OECONF_append_armeb =  --disable-smp-support --disable-hipe
EXTRA_OECONF_append_mipsel =  --disable-smp-support --disable-hipe
  @@ -55,5 +56,6 @@ FILES_${PN}-staticdev += ${libdir}/*/*/*/*.a
  ${libdir}/*/*/*/*/*.a ${libdir}/*/
 
FILES_${PN}-libs-dbg +=  ${libdir}/erlang/*/.debug
 ${libdir}/erlang/*/*/.debug ${libdir}/erlang/*/*/*/.debug
 ${libdir}/erlang/*/*/*/*/.debug ${libdir}/erlang/*/*/*/*/*/.debug 
 
  +SRC_URI += file://erlang-fix-build-issue-in-Yocto.patch
SRC_URI[md5sum] = dd6c2a4807551b4a8a536067bde31d73
SRC_URI[sha256sum] =
 5bc34fc34fc890f84bae7ff1f7c81fbec2c9aa28a0ef51a57d7a8192204d8aa2
 
 


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

[yocto] [meta-cloud-services][PATCH v2] erlang: skip the host library path check to fix cross-compile issue

[Zhenhua Luo]

Below is the error message:
ERROR: This autoconf log indicates errors, it looked at host include and/or 
library paths while determining system capabilities.
Rerun configure task after fixing this.

Signed-off-by: Zhenhua Luo zhenhua@freescale.com
---
 .../erlang/erlang-fix-build-issue-in-Yocto.patch   | 25 ++
 .../recipes-devtools/erlang/erlang_R15B.bb |  1 +
 2 files changed, 26 insertions(+)
 create mode 100644 
meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch

diff --git 
a/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
 
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
new file mode 100644
index 000..2d4b7b5
--- /dev/null
+++ 
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
@@ -0,0 +1,25 @@
+Upstream-Status: Inappropriate [The fix is specific to Yocto build env]
+
+Skip host library path check to fix following Yocto insane check issue: 
+ERROR: This autoconf log indicates errors, it looked at host include and/or 
library paths while determining system capabilities.
+Rerun configure task after fixing this.
+
+Signed-off-by: Zhenhua Luo zhenhua@freescale.com
+
+--- otp_src_R15B/erts/configure.in.orig2011-12-14 04:22:11.0 
-0600
 otp_src_R15B/erts/configure.in 2013-11-19 04:15:33.694334610 -0600
+@@ -1469,10 +1469,10 @@
+   # ln -s libdlpi.so.1 $try_dlpi_lib/libdlpi.so
+   ])
+fi
+-   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
+-   unset -v try_dlpi_lib
+-   AC_MSG_NOTICE([Extending the search to include /lib])
+-   AC_CHECK_LIB(dlpi, dlpi_open)
++#   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
++#   unset -v try_dlpi_lib
++#   AC_MSG_NOTICE([Extending the search to include /lib])
++#   AC_CHECK_LIB(dlpi, dlpi_open)
+if test x$ac_cv_lib_dlpi_dlpi_open = xno; then
+   LDFLAGS=$save_ldflags
+fi
diff --git a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb 
b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
index 68d144b..d7fd310 100644
--- a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
+++ b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
@@ -55,5 +55,6 @@ FILES_${PN}-staticdev += ${libdir}/*/*/*/*.a 
${libdir}/*/*/*/*/*.a ${libdir}/*/
 
 FILES_${PN}-libs-dbg +=  ${libdir}/erlang/*/.debug 
${libdir}/erlang/*/*/.debug ${libdir}/erlang/*/*/*/.debug 
${libdir}/erlang/*/*/*/*/.debug ${libdir}/erlang/*/*/*/*/*/.debug 
 
+SRC_URI += file://erlang-fix-build-issue-in-Yocto.patch
 SRC_URI[md5sum] = dd6c2a4807551b4a8a536067bde31d73
 SRC_URI[sha256sum] = 
5bc34fc34fc890f84bae7ff1f7c81fbec2c9aa28a0ef51a57d7a8192204d8aa2
-- 
1.8.3.1


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

Re: [yocto] [meta-cloud-services][PATCH v2] erlang: skip the host library path check to fix cross-compile issue

[Zhenhua Luo]

I am checking if this modification is necessary, and will post a patch if it is 
needed. 


Best Regards,

Zhenhua


 -Original Message-
 From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
 Sent: Wednesday, November 20, 2013 9:46 PM
 To: Luo Zhenhua-B19537; yocto@yoctoproject.org
 Cc: Liu Ting-B28495; Guo Chunrong-B40290; Yu Zongchun-B40527
 Subject: Re: [meta-cloud-services][PATCH v2] erlang: skip the host
 library path check to fix cross-compile issue
 
 On 13-11-20 05:38 AM, Zhenhua Luo wrote:
  Below is the error message:
  ERROR: This autoconf log indicates errors, it looked at host include
 and/or library paths while determining system capabilities.
  Rerun configure task after fixing this.
 
 In your previous revision, you also had:
 
EXTRA_OECONF_append_powerpc =  --disable-smp-support --disable-hipe
 
 I had asked for it to be a separate patch. Is that part no longer
 required for your builds ?
 
 Bruce
 
 
  Signed-off-by: Zhenhua Luo zhenhua@freescale.com
  ---
.../erlang/erlang-fix-build-issue-in-Yocto.patch   | 25
 ++
.../recipes-devtools/erlang/erlang_R15B.bb |  1 +
2 files changed, 26 insertions(+)
create mode 100644
  meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-i
  n-Yocto.patch
 
  diff --git
  a/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue
  -in-Yocto.patch
  b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue
  -in-Yocto.patch
  new file mode 100644
  index 000..2d4b7b5
  --- /dev/null
  +++ b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-i
  +++ ssue-in-Yocto.patch
  @@ -0,0 +1,25 @@
  +Upstream-Status: Inappropriate [The fix is specific to Yocto build
  +env]
  +
  +Skip host library path check to fix following Yocto insane check issue:
  +ERROR: This autoconf log indicates errors, it looked at host include
 and/or library paths while determining system capabilities.
  +Rerun configure task after fixing this.
  +
  +Signed-off-by: Zhenhua Luo zhenhua@freescale.com
  +
  +--- otp_src_R15B/erts/configure.in.orig2011-12-14
 04:22:11.0 -0600
   otp_src_R15B/erts/configure.in 2013-11-19 04:15:33.694334610 -
 0600
  +@@ -1469,10 +1469,10 @@
  +   # ln -s libdlpi.so.1 $try_dlpi_lib/libdlpi.so
  +   ])
  +fi
  +-   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
  +-   unset -v try_dlpi_lib
  +-   AC_MSG_NOTICE([Extending the search to include /lib])
  +-   AC_CHECK_LIB(dlpi, dlpi_open)
  ++#   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
  ++#   unset -v try_dlpi_lib
  ++#   AC_MSG_NOTICE([Extending the search to include /lib])
  ++#   AC_CHECK_LIB(dlpi, dlpi_open)
  +if test x$ac_cv_lib_dlpi_dlpi_open = xno; then
  +   LDFLAGS=$save_ldflags
  +fi
  diff --git a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  index 68d144b..d7fd310 100644
  --- a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  +++ b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
  @@ -55,5 +55,6 @@ FILES_${PN}-staticdev += ${libdir}/*/*/*/*.a
  ${libdir}/*/*/*/*/*.a ${libdir}/*/
 
FILES_${PN}-libs-dbg +=  ${libdir}/erlang/*/.debug
 ${libdir}/erlang/*/*/.debug ${libdir}/erlang/*/*/*/.debug
 ${libdir}/erlang/*/*/*/*/.debug ${libdir}/erlang/*/*/*/*/*/.debug 
 
  +SRC_URI += file://erlang-fix-build-issue-in-Yocto.patch
SRC_URI[md5sum] = dd6c2a4807551b4a8a536067bde31d73
SRC_URI[sha256sum] =
 5bc34fc34fc890f84bae7ff1f7c81fbec2c9aa28a0ef51a57d7a8192204d8aa2
 
 


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

[yocto] [meta-cloud-services][PATCH] erlang: skip the host library path check to fix cross-compile issue

[Zhenhua Luo]

Signed-off-by: Zhenhua Luo zhenhua@freescale.com
---
 .../erlang/erlang-fix-build-issue-in-Yocto.patch   | 25 ++
 .../recipes-devtools/erlang/erlang_R15B.bb |  2 ++
 2 files changed, 27 insertions(+)
 create mode 100644 
meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch

diff --git 
a/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
 
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
new file mode 100644
index 000..2d4b7b5
--- /dev/null
+++ 
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
@@ -0,0 +1,25 @@
+Upstream-Status: Inappropriate [The fix is specific to Yocto build env]
+
+Skip host library path check to fix following Yocto insane check issue: 
+ERROR: This autoconf log indicates errors, it looked at host include and/or 
library paths while determining system capabilities.
+Rerun configure task after fixing this.
+
+Signed-off-by: Zhenhua Luo zhenhua@freescale.com
+
+--- otp_src_R15B/erts/configure.in.orig2011-12-14 04:22:11.0 
-0600
 otp_src_R15B/erts/configure.in 2013-11-19 04:15:33.694334610 -0600
+@@ -1469,10 +1469,10 @@
+   # ln -s libdlpi.so.1 $try_dlpi_lib/libdlpi.so
+   ])
+fi
+-   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
+-   unset -v try_dlpi_lib
+-   AC_MSG_NOTICE([Extending the search to include /lib])
+-   AC_CHECK_LIB(dlpi, dlpi_open)
++#   LDFLAGS=-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS
++#   unset -v try_dlpi_lib
++#   AC_MSG_NOTICE([Extending the search to include /lib])
++#   AC_CHECK_LIB(dlpi, dlpi_open)
+if test x$ac_cv_lib_dlpi_dlpi_open = xno; then
+   LDFLAGS=$save_ldflags
+fi
diff --git a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb 
b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
index 68d144b..8d8e28b 100644
--- a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
+++ b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
@@ -9,6 +9,7 @@ EXTRA_OEMAKE = BUILD_CC='${BUILD_CC}'
 
 EXTRA_OECONF = --with-ssl=${STAGING_DIR_HOST}${layout_exec_prefix}
 
+EXTRA_OECONF_append_powerpc =  --disable-smp-support --disable-hipe
 EXTRA_OECONF_append_arm =  --disable-smp-support --disable-hipe
 EXTRA_OECONF_append_armeb =  --disable-smp-support --disable-hipe
 EXTRA_OECONF_append_mipsel =  --disable-smp-support --disable-hipe
@@ -55,5 +56,6 @@ FILES_${PN}-staticdev += ${libdir}/*/*/*/*.a 
${libdir}/*/*/*/*/*.a ${libdir}/*/
 
 FILES_${PN}-libs-dbg +=  ${libdir}/erlang/*/.debug 
${libdir}/erlang/*/*/.debug ${libdir}/erlang/*/*/*/.debug 
${libdir}/erlang/*/*/*/*/.debug ${libdir}/erlang/*/*/*/*/*/.debug 
 
+SRC_URI += file://erlang-fix-build-issue-in-Yocto.patch
 SRC_URI[md5sum] = dd6c2a4807551b4a8a536067bde31d73
 SRC_URI[sha256sum] = 
5bc34fc34fc890f84bae7ff1f7c81fbec2c9aa28a0ef51a57d7a8192204d8aa2
-- 
1.8.3.1


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

[yocto] [meta-cloud-services][PATCH] python-horizon: remove nodejs from RDEPENDS of powerpc arch

[Zhenhua Luo]

Nodejs only supports arm, x86 and ia32 archs, it doesn't support powerpc.

Signed-off-by: Zhenhua Luo zhenhua@freescale.com
---
 meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb 
b/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
index fdd0bd0..edd8dae 100644
--- a/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
+++ b/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
@@ -63,8 +63,7 @@ FILES_${SRCNAME} = ${bindir}/* \
 ${datadir}/* \
 
 
-RDEPENDS_${PN} += nodejs \
-python-django \
+RDEPENDS_${PN} +=  python-django \
 python-django-appconf \
 python-django-compressor \
 python-django-openstack-auth \
@@ -80,6 +79,11 @@ RDEPENDS_${PN} += nodejs \
 python-lockfile \
 
 
+RDEPENDS_${PN}_arm +=  nodejs
+RDEPENDS_${PN}_i686 +=  nodejs
+RDEPENDS_${PN}_x86-64 +=  nodejs
+RDEPENDS_${PN}_ia32 +=  nodejs
+
 RDEPENDS_${SRCNAME} = ${PN}
 
 INITSCRIPT_PACKAGES = ${SRCNAME}
-- 
1.8.3.1


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

[yocto] [meta-fsl-ppc] hypervisor: add missing space character for PACKAGES_prepend

[Zhenhua Luo]

Signed-off-by: Zhenhua Luo b19...@freescale.com
---
 recipes-tools/embedded-hv/hypervisor_git.bb |4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/recipes-tools/embedded-hv/hypervisor_git.bb 
b/recipes-tools/embedded-hv/hypervisor_git.bb
index 50697fc..3a3f605 100644
--- a/recipes-tools/embedded-hv/hypervisor_git.bb
+++ b/recipes-tools/embedded-hv/hypervisor_git.bb
@@ -3,6 +3,8 @@ SECTION = embedded-hv
 LICENSE = BSD
 LIC_FILES_CHKSUM = 
file://README;endline=22;md5=0655bbc3b7d7166c30c87208b4e23cf0
 
+PR = r1
+
 DEPENDS = u-boot-mkimage-native
 
 inherit deploy
@@ -74,6 +76,6 @@ do_deploy_append() {
 }
 
 ALLOW_EMPTY_${PN} = 1
-PACKAGES_prepend = ${PN}-image ${PN}-partman
+PACKAGES_prepend = ${PN}-image ${PN}-partman 
 FILES_${PN}-image = /boot/
 FILES_${PN}-partman = ${bindir}/partman
-- 
1.7.9.5


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