[yocto] Legacy library find.pl will be removed from the Perl core distribution in the next major release
Hi , all The version of YP which I using is 1.6.2. When building the openssl, it appears the problem as following : ERROR: Function failed: do_configure (log file is located at /home/ectrs/poky/cortexta8_build/tmp/work/i686-linux/openssl-native/1.0.1j-r0/temp/log.do_configure.6021) ERROR: Logfile of failure stored in: /home/ectrs/poky/cortexta8_build/tmp/work/i686-linux/openssl-native/1.0.1j-r0/temp/log.do_configure.6021 Log data follows: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | Legacy library find.pl will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at perlpath.pl, line 7. | Usage: Configure [no- ...] [enable- ...] [experimental- ...] [-Dxxx] [-lxxx] [-Lxxx] [-fxxx] [-Kxxx] [no-hw-xxx|no-hw] [[no-]threads] [[no-]shared] [[no-]zlib|zlib-dynamic] [no-asm] [no-dso] [no-krb5] [sctp] [386] [--prefix=DIR] [--openssldir=OPENSSLDIR] [--with-xxx[=vvv]] [--test-sanity] os/compiler[:flags] | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/ectrs/poky/cortexta8_build/tmp/work/i686-linux/openssl-native/1.0.1j-r0/temp/log.do_configure.6021) ERROR: Task 514 (virtual:native:/home/ectrs/poky/meta/recipes-connectivity/openssl/openssl_1.0.1j.bb, do_configure) failed with exit code '1' How to resolve this problem? If you know , please tell me . Thank you very much. Neil Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ld: cannot find crti.o: No such file or directory
Hi, all
I use the 1.8 YP to build the ccgi, the receip of ccgi as this:
SUMMARY = Add ccgi lib to rootfs
HOMEPAGE = http://sourceforge.net/projects/libccgi/?source=typ_redirect;
LICENSE = GPLv2
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
LIC_FILES_CHKSUM = file://COPYING;md5=d32239bcb673463ab874e80d47fae504
FILES_${PN}_dev = ${libdir}/* ${includedir}/*
SRC_URI = file://${PN}-${PV}.tgz \
file://0001-modify-the-source-code-to-match-the-G4-code.patch \
S = ${WORKDIR}/${PN}-${PV}
PARALLEL_MAKEINST=prefix=${D}/usr
EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX}'
do_compile() {
oe_runmake
OPENSSL_INCLUDE=${TOPDIR}/tmp/sysroots/${MACHINE}/usr/include
}
It appears the error as follows:
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find crti.o: No such file or directory
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find crtbeginS.o: No such file or directory
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find -lgcc
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find -lgcc_s
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find -lpthread
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find -lc
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find -lgcc
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find -lgcc_s
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find crtendS.o: No such file or directory
|
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld:
cannot find crtn.o: No such file or directory
In fact , I can find the crti.o in
/home/ectrs/poky/coretexa8/tmp/sysroots/i686-linux/usr/ directory.
How to resolve this problem? If you know ,please tell me .
Thanks
Neil
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] The problem of do_rootfs_append
Hi, nico
Thank you for your reply.
But I found that there are others use do_rootfs_append() when searching on the
Internet.
If I want to remove the directory in do_rootfs() task, how can I to do it ?
Tanks
Neil
-Original Message-
From: Nicolas Dechesne [mailto:nicolas.deche...@linaro.org]
Sent: Thursday, January 22, 2015 4:20 PM
To: Wu, Neil [CLIMATE/RS/CN]
Cc: Yocto list discussion
Subject: Re: [yocto] The problem of do_rootfs_append
On Thu, Jan 22, 2015 at 9:13 AM, neil...@emerson.com wrote:
Hi, all
I'm building specific rootfs image. Add the do_rootfs_append() task in
core-image-specific.bb,
core-image-specific.bb:
SUMMARY = creaet the customer rootfs
require ${TOPDIR}/../meta/recipes-core/images/core-image-minimal.bb
IMAGE_INSTALL = readline-dev linux-libc-headers-dev json-glib busybox-udhcpc
do_rootfs_append() {
cp -rf ${IMAGE_ROOTFS}/data/etc/ ${IMAGE_ROOTFS}/etc/
rm -rf ${IMAGE_ROOTFS}/data/etc/
}
It always meet the error as follows:
ERROR: ExpansionError during parsing
/home/ectrs/poky/meta-emerson-ecosys/recipes-core/images/core-image-ecosys.bb:
Failure expanding variable do_rootfs: IndentationError: unexpected indent
(string, line 14)
I'm pleasant receive your reply. If you know how to solve it , please help me
.
Thank you very much.
do_rootfs() in a Python function, not Shell in image.bbclass, so while
I have never tried that specifically, i guess you cannot append a
Shell snipped in that case.
cheers
nico
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] The problem of do_rootfs_append
Hi, all
I'm building specific rootfs image. Add the do_rootfs_append() task in
core-image-specific.bb,
core-image-specific.bb:
SUMMARY = creaet the customer rootfs
require ${TOPDIR}/../meta/recipes-core/images/core-image-minimal.bb
IMAGE_INSTALL = readline-dev linux-libc-headers-dev json-glib busybox-udhcpc
do_rootfs_append() {
cp -rf ${IMAGE_ROOTFS}/data/etc/ ${IMAGE_ROOTFS}/etc/
rm -rf ${IMAGE_ROOTFS}/data/etc/
}
It always meet the error as follows:
ERROR: ExpansionError during parsing
/home/ectrs/poky/meta-emerson-ecosys/recipes-core/images/core-image-ecosys.bb:
Failure expanding variable do_rootfs: IndentationError: unexpected indent
(string, line 14)
I'm pleasant receive your reply. If you know how to solve it , please help me .
Thank you very much.
Neil
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] The problem of do_rootfs_append
Hi, nico Thank you for your help. I have resolved the problem using IMAGE_POSTPROCESS_COMMAND in core-image-specific.bb. Neil -Original Message- From: Nicolas Dechesne [mailto:nicolas.deche...@linaro.org] Sent: Thursday, January 22, 2015 4:41 PM To: Wu, Neil [CLIMATE/RS/CN] Cc: Yocto list discussion Subject: Re: [yocto] The problem of do_rootfs_append On Thu, Jan 22, 2015 at 9:31 AM, neil...@emerson.com wrote: Thank you for your reply. But I found that there are others use do_rootfs_append() when searching on the Internet. If I want to remove the directory in do_rootfs() task, how can I to do it ? do_rootfs was a Shell function in the past, it was changed to Python last year or so. if you want to post process an image, you can use IMAGE_POSTPROCESS_COMMAND variable and add your own functions there. cheers -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] the problem of poky 1.7 when building the custom rootfs
Hi ,all I try to build my custom image , The problem appears as follows: ERROR: Trying to resolve runtime dependency eglibc resulted in conflicting PREFERRED_PROVIDER entries being found. The providers found were: ['/home/ectrs/poky/meta/recipes-core/glibc/glibc-initial_2.20.bb', 'virtual:nativesdk:/home/ectrs/poky/meta/recipes-core/glibc/glibc-initial_2.20.bb'] The PREFERRED_PROVIDER entries resulting in this conflict were: ['PREFERRED_PROVIDER_virtual/arm-poky-linux-gnueabi-libc-initial = glibc-initial', 'PREFERRED_PROVIDER_virtual/nativesdk-i686-pokysdk-linux-libc-initial = nativesdk-glibc-initial'] Do you know how to resolve it ? Please help me . Thank you very much. Best wishes Neil -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] can't find the source code of kernel
Hi, Bruce
Thank you very much for your help. My problem have solved. Before, I was
working in master branch.
Switch to a new branch, I find the source directory ,what included the kernel
source code, in linux-qemuarm-standard-build.
Neil
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Friday, January 16, 2015 12:36 PM
To: Wu, Neil [CLIMATE/RS/CN]; yocto@yoctoproject.org
Subject: Re: [yocto] can't find the source code of kernel
On 2015-01-15 8:13 PM, neil...@emerson.com wrote:
Hi, Bruce
Thank you for your reply.
In the WORKDIR , it just has linux-qemuarm-standard-build and not have the
linux.
Are you sure you are building Yocto 1.7 and not the master branch ?
Until about a month ago, every build had the source along side the
split build directory .. in a directory called linux. But as I
mentioned, we are working to move the kernel to build out of the
sysroot/shared working directory.
My WORKDIR directory is
~/poky/build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0,
but I don't find the tarball of linux-14.24
in download directory. It has tarball linux-17.7.tar.xz.
Do you think whether these is the reason?
They shouldn't be related. But that tar.xz you reference above is
clearly from some other kernel build than the linux yocto variant.
I don't know how to set the version of linux when the project building the
image.
Maybe, I set the linux to 17.7 version, the problem can solve.
I'm not sure how you are getting a 17.7 tarball, but the linux-yocto
tree builds from a git repository, not a tarball.
In that directory where you see the qemuarm build you should also see a
git.indirectionsymlink that points to the git tree in downloads/git2/
Cheers,
Bruce
Do you have any other better suggestion? Thank you very much.
Neil
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Thursday, January 15, 2015 9:05 PM
To: Wu, Neil [CLIMATE/RS/CN]; yocto@yoctoproject.org
Subject: Re: [yocto] can't find the source code of kernel
On 2015-01-15 5:03 AM, neil...@emerson.com wrote:
Hi ,all
The version of poky is 1.7. I build the linux-yocto is successful .
bitbake linux-yocto
But, why I can't find the source code of linux in ${WORKDIR}.
It should be there (note: it is about to move in master, but not in 1.7.1).
In WORKDIR, you have linux (the source) and linux-$MACHINE-build (the
build).
Bruce
Best wishes
Neil
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] dependency eglibc resulted in conflicting PREFERRED_PROVIDER entries being found
Hi ,all I try to build my custom image , The problem appears as follows: ERROR: Trying to resolve runtime dependency eglibc resulted in conflicting PREFERRED_PROVIDER entries being found. The providers found were: ['/home/ectrs/poky/meta/recipes-core/glibc/glibc-initial_2.20.bb', 'virtual:nativesdk:/home/ectrs/poky/meta/recipes-core/glibc/glibc-initial_2.20.bb'] The PREFERRED_PROVIDER entries resulting in this conflict were: ['PREFERRED_PROVIDER_virtual/arm-poky-linux-gnueabi-libc-initial = glibc-initial', 'PREFERRED_PROVIDER_virtual/nativesdk-i686-pokysdk-linux-libc-initial = nativesdk-glibc-initial'] Do you know how to resolve it ? Please help me . Thank you very much. Best wishes Neil -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] can't find the source code of kernel
Hi ,all
The version of poky is 1.7. I build the linux-yocto is successful .
bitbake linux-yocto
But, why I can’t find the source code of linux in ${WORKDIR}.
Best wishes
Neil
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] can't find the source code of kernel
Hi, Bruce
Thank you for your reply.
In the WORKDIR , it just has linux-qemuarm-standard-build and not have the
linux.
My WORKDIR directory is
~/poky/build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0,
but I don't find the tarball of linux-14.24
in download directory. It has tarball linux-17.7.tar.xz.
Do you think whether these is the reason?
I don't know how to set the version of linux when the project building the
image.
Maybe, I set the linux to 17.7 version, the problem can solve.
Do you have any other better suggestion? Thank you very much.
Neil
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Thursday, January 15, 2015 9:05 PM
To: Wu, Neil [CLIMATE/RS/CN]; yocto@yoctoproject.org
Subject: Re: [yocto] can't find the source code of kernel
On 2015-01-15 5:03 AM, neil...@emerson.com wrote:
Hi ,all
The version of poky is 1.7. I build the linux-yocto is successful .
bitbake linux-yocto
But, why I can't find the source code of linux in ${WORKDIR}.
It should be there (note: it is about to move in master, but not in 1.7.1).
In WORKDIR, you have linux (the source) and linux-$MACHINE-build (the
build).
Bruce
Best wishes
Neil
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] problem of install kernel module(*.ko) to rootfs folder
Hi all, First of all , merry Christmas. I run menuconfig and save the .config as following: CONFIG_SPI_DEV_INTERFACE=m CONFIG_PACKAGE_kmod-usb-core=m Then I build the linux-yocto and core-image-minimal : Bitbake linux-yocto Bitbake core-image-minimal I expected all the kernel module will install in core-image-minimal rootfs, but , in the ./lib/modules/3.4.44-G4 , I just find modules.alias, modules.alias.bin , modules.builtin.bin, modules.dep ... It have nothing kernel modules (*.ko) file in ./lib/modules/. How to install the *.ko to rootfs automatically ? Someone tell me to change the .config file as these : CONFIG_SPI_DEV_INTERFACE=y CONFIG_PACKAGE_kmod-usb-core=y I have test it what will build the kernel modules (*.ko ) to kernel image, that's not what I need. so , I just want to know . how to install the kernel modules (*.ko) to core-image-minimal rootfs ? If you know it , please help me . Thank you very much. Neil -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problem of install kernel module(*.ko) to rootfs folder
Hi Raj, Thank you for your reply. I have resolved the problem. Thank you!! Neil -Original Message- From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Thursday, December 25, 2014 11:26 AM To: Wu, Neil [CLIMATE/RS/CN] Cc: yocto@yoctoproject.org Subject: Re: [yocto] problem of install kernel module(*.ko) to rootfs folder On Wed, Dec 24, 2014 at 7:08 PM, neil...@emerson.com wrote: Hi all, First of all , merry Christmas. I run menuconfig and save the .config as following: CONFIG_SPI_DEV_INTERFACE=m CONFIG_PACKAGE_kmod-usb-core=m Then I build the linux-yocto and core-image-minimal : Bitbake linux-yocto Bitbake core-image-minimal I expected all the kernel module will install in core-image-minimal rootfs, but , in the ./lib/modules/3.4.44-G4 , I just find modules.alias, modules.alias.bin , modules.builtin.bin, modules.dep … It have nothing kernel modules (*.ko) file in ./lib/modules/. How to install the *.ko to rootfs automatically ? Someone tell me to change the .config file as these : CONFIG_SPI_DEV_INTERFACE=y CONFIG_PACKAGE_kmod-usb-core=y I have test it what will build the kernel modules (*.ko ) to kernel image, that’s not what I need. so , I just want to know . how to install the kernel modules (*.ko) to core-image-minimal rootfs ? If you know it , please help me . well its a minimal-image so all modules are excluded. You can build core-image-basic and it should have it or you can do something like MACHINE_EXTRA_RRECOMMENDS = kernel-modules in your machine.conf Thank you very much. Neil -- ___ 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] problem of toolchain install directrory
Hello ,all I build the toolchain via bitbake core-image-minimal –c populate_sdk. Then I install the toolchain. If I install the toolchain in default directory(default: /opt/poky/1.7.1), everything is ok. But, if I not install in the default directory, it will appears the problem that can’t find the system header files. Example: stdio.h Why is this ? Whether I need to do some other operation. If you know please help me ! Thank you very much. Best wishes Neil -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problem of toolchain install directrory
Hello Liviu, Thank you very much for your reply. I got a very useful information from your reply. At the beginning , I want to add the cross compiler to eclipse project and not use the default installer directory, but it appears the above problem. In eclipse project, the setting as these: Properties -- Setting--CrossSetting --Prefilx: arm-poky-linux-gnueabi- Properties--Setting -- CrossSetting--Path: /opt/poky/mycompiler/sysroots/ i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi You give me the idea to add the sysroot path: Properties -- Setting -- Cross GCC compiler -MisCellaneous: --sysroot=/opt/poky/mycompiler/sysroots/ armv5te-poky-linux-gnueabi Now, everything is ok . Thank you again for your help. Best wishes Neil From: Liviu Gheorghisan [mailto:liviu.gheorghi...@enea.com] Sent: Wednesday, December 17, 2014 5:47 PM To: Wu, Neil [CLIMATE/RS/CN]; yocto@yoctoproject.org Subject: Re: [yocto] problem of toolchain install directrory Hello Neil, Your problem is that the toolchain is installed with the location of the sysroot hardcoded as the default installation path for the tool-chain. You can see this location with: $ arm-poky-linux-gnueabi-gcc --print-sysroot // or whatever cross-compiler you built However, after you source the environment script for the toolchain: $ source environment-setup-armv7a-vfp-neon-poky-linux-gnueabi the environment variables related to the toolchain will be updated accordingly, taking care of this problem. So, use $CC instead of directly calling the gcc cross compiler arm-poky-linux-gnueabi-gcc (or whatever the platform you're building for). Check the difference with this: $ echo $CC arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/home/livghe/work/ab/sdk/sysroots/armv7a-vfp-neon-poky-linux-gnueabi $ $CC --print-sysroot // uses the correct sysroot /home/livghe/work/ab/sdk/sysroots/armv7a-vfp-neon-poky-linux-gnueabi $ $ arm-poky-linux-gnueabi-gcc --print-sysroot // uses the sysroot from the default instalation path, where it's not present. /opt/poky/4.0/sysroots/armv7a-vfp-neon-poky-linux-gnueabi So, you should always use the env variables ($CC, $AR, $LDFLAGS, etc) after sourcing the environment script from the toolchain instalation path, and not the toolchain executables directly, because the environment variables add some useful flags, not only related to the sysroot, but also to the type of CPU, etc. - Liviu On 12/17/2014 11:30 AM, neil...@emerson.commailto:neil...@emerson.com wrote: Hello ,all I build the toolchain via bitbake core-image-minimal -c populate_sdk. Then I install the toolchain. If I install the toolchain in default directory(default: /opt/poky/1.7.1), everything is ok. But, if I not install in the default directory, it will appears the problem that can't find the system header files. Example: stdio.h Why is this ? Whether I need to do some other operation. If you know please help me ! Thank you very much. Best wishes Neil -- Liviu Gheorghisan Software Engineer http://www.enea.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Luajit Compile Error
Hello everyone,
I want to add some command in do_rootfs() task, so I add the information in
core-image-minimal.bb like following :
.
.
do_rootfs_append() {
.
.
.
}
.
.
But ,it always appears the error as this :
ERROR: ExpansionError during parsing
/home/etcrs/poky/meta/recipes-core/glib-2.0/glib-2.0_2.38.2.bb: Failure
expanding variable do_package: SyntaxError: invalid syntax (string, line 81)
If you know how to do this ,please tell me ! Thank you very much!
Neil
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] add files to dirctory in packages-split
Hi all, I want to add some files to the specified directory what in packages-split. How to do it ? Thank you Neil -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] add files to dirctory in packages-split
Hi Raj,
Thank you very much for your reply. I have try to do like you say.
I’m compiling the glib-2.0, need to add the link file of one library to
glib-2.0 package.
So I add the command like following :
FILES_${PN} += “${libdir}/libgio-2.0.so”
But , it can’t success.
Do you know whether need to do other thing?
Neil
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Thursday, December 11, 2014 6:05 PM
To: Wu, Neil [CLIMATE/RS/CN]
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] add files to dirctory in packages-split
On Dec 11, 2014, at 1:35 AM, neil...@emerson.commailto:neil...@emerson.com
wrote:
Hi all,
I want to add some files to the specified directory what in packages-split.
How to do it ?
FILES_name-of-package += “/path/to/file
Thank you
Neil
--
___
yocto mailing list
yocto@yoctoproject.orgmailto:yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] add files to dirctory in packages-split
Hello Raj,
Thank you for your help. The problem have solved.
Neil
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Friday, December 12, 2014 10:48 AM
To: Wu, Neil [CLIMATE/RS/CN]
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] add files to dirctory in packages-split
On Dec 11, 2014, at 5:59 PM, neil...@emerson.commailto:neil...@emerson.com
wrote:
Hi Raj,
Thank you very much for your reply. I have try to do like you say.
I’m compiling the glib-2.0, need to add the link file of one library to
glib-2.0 package.
So I add the command like following :
FILES_${PN} += “${libdir}/libgio-2.0.so”
But , it can’t success.
.so are usually treated to be includes in -dev packages by default
first you need to figure out if you really need .so on target, many times you
don’t
some packages still do ( don’t use .so versioning ) then you would need
something like
FILES_SOLIBSDEV =
SOLIBS = .so
INSANE_SKIP_${PN} += dev-so
Do you know whether need to do other thing?
Neil
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Thursday, December 11, 2014 6:05 PM
To: Wu, Neil [CLIMATE/RS/CN]
Cc: yocto@yoctoproject.orgmailto:yocto@yoctoproject.org
Subject: Re: [yocto] add files to dirctory in packages-split
On Dec 11, 2014, at 1:35 AM, neil...@emerson.commailto:neil...@emerson.com
wrote:
Hi all,
I want to add some files to the specified directory what in packages-split.
How to do it ?
FILES_name-of-package += “/path/to/file
Thank you
Neil
--
___
yocto mailing list
yocto@yoctoproject.orgmailto:yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Compile th nativesdk-automake fail.
Hi all : It appears the following problem when compiling the nativesdk-automake: | Can't locate Text/Tabs.pm in @INC (@INC contains: //usr/lib/perl/5.14.3 //usr/lib/perl //usr/lib/perl/5.14.3 /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/site_perl/5.14.3/ /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/site_perl/5.14.3 /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/vendor_perl/5.14.3/ /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/vendor_perl/5.14.3 /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/5.14.3/ /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/5.14.3 /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/lib/perl/5.14.3 .) at /home/etcrs/poky/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-automake/1.14-r0/automake-1.14/doc/help2man line 25. | BEGIN failed--compilation aborted at /home/etcrs/poky/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-automake/1.14-r0/automake-1.14/doc/help2man line 25. If someone has also encountered such a problem, please tell me how to resolve it! Thank you ! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can't find the header files after install adt_installer.tar.gz
Thank you for your reply. I just move the adt_installer.tar.gz to another pc which don't have yocto project. Install the adt_installer and execute the environment-setup-armv5te-poky-linux-gnueabi Then compile the hello.c arm-poky-linux-gnueabi-gcc hello.c -o hello I don't know whether need to do other thing? -Original Message- From: Nick Krause [mailto:xerofo...@gmail.com] Sent: Thursday, November 13, 2014 11:05 PM To: Wu, Neil [CLIMATE/RS/CN] Cc: yocto@yoctoproject.org Subject: Re: [yocto] Can't find the header files after install adt_installer.tar.gz Have you read the yocto docs on ADT for building correctly your development kit, seems to me rather trivial error in either your build or bitbake recipe for hello world. Cheers Nick On Thu, Nov 13, 2014 at 4:43 AM, neil...@emerson.com wrote: Hi all : I have installed the adt_installer .tar.gz like fllowing: $ cd ~ $ tar -xjf adt_installer.tar.bz2 $ cd adt-installer $ ./adt_installer Because the YOCTOADT_TARGET_SYSROOT_LOC_arm=$HOME/test-yocto/$YOCTOADT_TARGET_MAC HINE_arm in adt_installer.conf file , then I extract the myself Root Filesystem: $source /opt/poky/1.7/environment-setup-i586-poky-linux $ runqemu-extract-sdk ~/Downloads/core-image-arm-rootfs.tar.bz2 $HOME/ test-yocto/ qemuarm/ Try to compile the “Helloworld”, it apper this error: hello.c:1:19: fatal error: stdio.h: No such file or directory Do you know how to resolve the issue? Please help me ! Thank you very much! -- ___ 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] Can not generate the ccgi-${PV} package
Hi, all
I try to compile libccgi .
At end , I don't why can't create the standard ccgi-${PV} package.
The just create ccgi-dbg-${PV} ccgi-dev-${PV}, do you know why??
The following is my recipes .bb file:
SUMMARY = Add ccgi lib to rootfs
HOMEPAGE = http://sourceforge.net/projects/libccgi/?source=typ_redirect;
LICENSE = GPLv2
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
LIC_FILES_CHKSUM = file://COPYING;md5=d32239bcb673463ab874e80d47fae504
FILES_${PN} = /usr \
/usr/include \
/usr/lib \
/usr/include/ccgi.h \
/usr/lib/libccgi.so \
SRC_URI = file://${PN}-${PV}.tar.gz
S = ${WORKDIR}/${PN}-${PV}
PARALLEL_MAKEINST=prefix=${D}/usr
EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX}'
do_install () {
install -d ${D}${includedir}
install -d ${D}${libdir}
install -m 0755 ${S}/*.h ${D}${includedir}
install -m 0755 ${S}/*.so ${D}${libdir}
}
Thank youBest regards
Neil Wu
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can not generate the ccgi-${PV} package
Hi, ting:
Thank you very much for your answer. My problem has been solved
If I don't have this ccgi-${PV} package ,although it is empty, yocto will
apper an error when adding the ccgi recipes.
Thank you again for your help.
From: ting@freescale.com [mailto:ting@freescale.com]
Sent: Friday, November 07, 2014 11:17 AM
To: Wu, Neil [CLIMATE/RS/CN]
Cc: yocto@yoctoproject.org
Subject: RE: Can not generate the ccgi-${PV} package
From: yocto-boun...@yoctoproject.orgmailto:yocto-boun...@yoctoproject.org
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of
neil...@emerson.commailto:neil...@emerson.com
Sent: Friday, November 07, 2014 10:44 AM
To: yocto@yoctoproject.orgmailto:yocto@yoctoproject.org
Subject: [yocto] Can not generate the ccgi-${PV} package
Hi, all
I try to compile libccgi .
At end , I don't why can't create the standard ccgi-${PV} package.
The just create ccgi-dbg-${PV} ccgi-dev-${PV}, do you know why??
The following is my recipes .bb file:
SUMMARY = Add ccgi lib to rootfs
HOMEPAGE = http://sourceforge.net/projects/libccgi/?source=typ_redirect;
LICENSE = GPLv2
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
LIC_FILES_CHKSUM =
file://COPYING;md5=d32239bcb673463ab874e80d47fae504file:///\\COPYING;md5=d32239bcb673463ab874e80d47fae504
FILES_${PN} = /usr \
/usr/include \
/usr/lib \
/usr/include/ccgi.h \
/usr/lib/libccgi.so \
SRC_URI = file://${PN}-${PV}.tar.gzfile:///\\$%7bPN%7d-$%7bPV%7d.tar.gz
S = ${WORKDIR}/${PN}-${PV}
PARALLEL_MAKEINST=prefix=${D}/usr
EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX}'
do_install () {
install -d ${D}${includedir}
install -d ${D}${libdir}
install -m 0755 ${S}/*.h ${D}${includedir}
install -m 0755 ${S}/*.so ${D}${libdir}
}
There is no file to be packaged as ${PN}. You can added below line to generate
it.
ALLOW_EMPTY_${PN} = 1
-Ting
Thank youBest regards
Neil Wu
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] samba tdb compile error！
Hi all, I creat the recipes of the samba tdb, compile the x86 package is ok ,but it apper an error when I ‘m compiling the arm package , like the following : Build Configuration: BB_VERSION= 1.22.0 BUILD_SYS = i686-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = qemuarm DISTRO= poky DISTRO_VERSION= 1.6.1 TUNE_FEATURES = armv5 thumb dsp TARGET_FPU= soft meta meta-yocto meta-yocto-bsp meta-G4 = daisy:525ec71e2c8dde72499f4e4cc6766f6db9c83e90 NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_configure (log file is located at /home/etcrs/poky/build/tmp/work/armv5te-poky-linux-gnueabi/g4tdb/1.3.1-r0/temp/log.do_configure.20145) ERROR: Logfile of failure stored in: /home/etcrs/poky/build/tmp/work/armv5te-poky-linux-gnueabi/g4tdb/1.3.1-r0/temp/log.do_configure.20145 Log data follows: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | Checking for program gcc or cc : ['arm-poky-linux-gnueabi-gcc', '-march=armv5te', '-marm', '-mthumb-interwork', '--sysroot=/home/etcrs/poky/build/tmp/sysroots/qemuarm'] | Checking for program ar : arm-poky-linux-gnueabi-ar | Checking for program ranlib : arm-poky-linux-gnueabi-ranlib | Checking for gcc : ok | Checking for program git : /opt/poky/1.6.1/sysroots/i686-pokysdk-linux/usr/bin/git | Check for -MD: yes | Checking for program gdb : /usr/bin/gdb | Checking build system: Linux SiteSupervisor 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:47:59 UTC 2014 i686 i686 i686 GNU/Linux | Checking for header sys/utsname.h: yes | Checking uname sysname type : Traceback (most recent call last): | File ./buildtools/bin/waf, line 76, in module | Scripting.prepare(t, cwd, VERSION, wafdir) | File /home/etcrs/poky/build/tmp/work/armv5te-poky-linux-gnueabi/g4tdb/1.3.1-r0/tdb-1.3.1/buildtools/wafadmin/Scripting.py, line 145, in prepare If you know the solution, please help me! Thank youBest regards Neil Wu -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] create_image.tar fail
Hi, I use the yocto-bsp tools to creat a new bsp layer, I found this problem like following : Yoctto-bsp creat myx86 quem Traceback (most recent call last): File /home/etcrs/poky/scripts/yocto-bsp, line 150, in module ret = main() File /home/etcrs/poky/scripts/yocto-bsp, line 145, in main invoke_subcommand(args, parser, yocto_bsp_help_usage, subcommands) File /home/etcrs/poky/scripts/lib/bsp/help.py, line 73, in invoke_subcommand subcommands.get(args[0], subcommand_error)[0](args[1:], usage) File /home/etcrs/poky/scripts/yocto-bsp, line 89, in yocto_bsp_create_subcommand yocto_bsp_create(machine, karch, scripts_path, bsp_output_dir, options.codedump, options.properties_file) File /home/etcrs/poky/scripts/lib/bsp/engine.py, line 1450, in yocto_bsp_create yocto_common_create(machine, arch, scripts_path, bsp_output_dir, codedump, properties_file, properties) SyntaxError: function specified for 'gen' property returned nothing : input type:choicelist name:new_kbranch nameappend:i386 gen:bsp.kernel.all_branches branches_base:standard:standard/common-pc prio:20 msg:Please choose a machine branch to base this BSP on: default:standard/common-pc/base How to resolve this problem ? If you know ,please tell me. Thanks very much. Thank youBest regards Neil Wu -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] create_image.tar fail
Hello , I meet one problem like following when I compiling Yocto project 1.6.1. create_image.ext3 ... NOTE: Running image creation script for tar: /home/etcrs/poky-daisy-11.0.1/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/temp/create_image.tar ... ERROR: Error: The image creation script '/home/etcrs/poky-daisy-11.0.1/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/temp/create_image.tar' returned 1: .. bzip2: invalid option -- 'k' BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) multi-call binary. Usage: bzip2 [OPTIONS] [FILE]... Compress FILEs (or stdin) with bzip2 algorithm -1..9 Compression level -dDecompress -c Write to stdout -f Force WARNING: exit code 1 from a shell command. DEBUG: Python function do_rootfs finished ERROR: Function failed: do_rootfs How to resolve this problem ? If you know ,please tell me. Thanks very much. Thank youBest regards Neil Wu -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] create_image.tar fail
Hi Burton : You are so great! Thank you very much .My problem has resolved. Although I don't install the busybox, but I find the busybox-static and ubuntu-standard in my system. Afer remove them , compiling is successful. busybox-static: /usr/share/doc/busybox-static/examples/udhcp/sample.renew busybox-static: /usr/share/doc/busybox-static/examples/mdev_fat.conf busybox-static: /usr/share/doc/busybox-static/examples/mdev.conf busybox-static: /usr/share/doc/busybox-static/examples busybox-static: /usr/share/doc/busybox-static/examples/udhcp/sample.nak Finally, sincerely thanks for your help. -Original Message- From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Monday, September 15, 2014 6:12 PM To: Wu, Neil [CLIMATE/RS/CN] Cc: yocto@yoctoproject.org Subject: Re: [yocto] create_image.tar fail On 15 September 2014 09:48, neil...@emerson.com wrote: BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) multi-call binary. Its using busybox's tar, don't do this. Either uninstall busybox, or change the alternatives so that /usr/bin/tar is GNU tar, not busybox tar. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
