Re: [yocto] Header-Files of DEPEND recipe not found
But not within CMakeLists.txt? At least this is not working, cmake is handling = as a normal character. I guess I have to pass a parameter within my *.bb to cmake containing the sysroot path 2015-08-10 22:36 GMT+02:00 Khem Raj raj.k...@gmail.com: On Mon, Aug 10, 2015 at 12:08 PM, yocto yocto yoctomailingl...@gmail.com wrote: SET(SOCI_INCLUDEDIR /home/my-PC/development/2015-08-04_edison-src/edison-src/build/tmp/sysroots/edison/usr/include/soci) everything worked fine. Is there any way to get the path /home/my-PC/development/2015-08-04_edison-src/edison-src/build/tmp/sysroots/edison/ within CMakeLists.txt automatically? you can use =/usr/include/soci which will prepend sysroot automatically. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Header-Files of DEPEND recipe not found
Maybe this is of interest, here is my solution:
In CMakeLists.txt
SET(BITBAKE_SYSROOT CACHE STRING Description)
SET(SOCI_INCLUDEDIR ${BITBAKE_SYSROOT}/usr/include/soci)
So if BITBAKE_SYSROOT is not passed the compiler takes /usr/include/soci as
usual. My *.bb contains:
EXTRA_OECMAKE = -DBITBAKE_SYSROOT:STRING=${STAGING_DIR_HOST}
So when using bitbake the appropriate prefix will be added.
2015-08-11 8:36 GMT+02:00 yocto yocto yoctomailingl...@gmail.com:
But not within CMakeLists.txt? At least this is not working, cmake is
handling = as a normal character. I guess I have to pass a parameter
within my *.bb to cmake containing the sysroot path
2015-08-10 22:36 GMT+02:00 Khem Raj raj.k...@gmail.com:
On Mon, Aug 10, 2015 at 12:08 PM, yocto yocto
yoctomailingl...@gmail.com wrote:
SET(SOCI_INCLUDEDIR
/home/my-PC/development/2015-08-04_edison-src/edison-src/build/tmp/sysroots/edison/usr/include/soci)
everything worked fine. Is there any way to get the path
/home/my-PC/development/2015-08-04_edison-src/edison-src/build/tmp/sysroots/edison/
within CMakeLists.txt automatically?
you can use =/usr/include/soci which will prepend sysroot automatically.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Header-Files of DEPEND recipe not found
I also did further research. The problem is that FIND_PACKAGE does not work for soci. For that reason one has to specify CMake variable such as SOCI_INCLUDEDIR manually. Using namespaces such as #include soci/soci.h is no solution: When enabling further backends such as postgresql this approach fails since these backends also require sth. like #include soci.h. Therefore changes in the soci sources files would be necessary. After manually changing CMakeLists.txt: SET(SOCI_INCLUDEDIR /usr/include/soci) to SET(SOCI_INCLUDEDIR /home/my-PC/development/2015-08-04_edison-src/edison-src/build/tmp/sysroots/edison/usr/include/soci) everything worked fine. Is there any way to get the path /home/my-PC/development/2015-08-04_edison-src/edison-src/build/tmp/sysroots/edison/ within CMakeLists.txt automatically? 2015-08-10 19:56 GMT+02:00 Khem Raj raj.k...@gmail.com: On Aug 10, 2015, at 4:50 AM, yocto yocto yoctomailingl...@gmail.com wrote: Please see the attachment for a simplified example. A library (consisting of 1 cpp and 1 header) is being built using soci. Compiling fails since soci.h is not found. 2015-08-10 13:16 GMT+02:00 Burton, Ross ross.bur...@intel.com: On 10 August 2015 at 12:13, yocto yocto yoctomailingl...@gmail.com wrote: However, when compiling my own recipe I get compiling errors (soci.h not found). I am 100% sure that I specified the correct paths. The headers are likely installed in the sysroot, but your script can't find them. The first step would be to verify that the sysroot does in fact have the headers installed in, and then you'll have to debug your configure scripts to find out why they don't find the headers. Sharing your recipe and sources will help here. yeah the CMakeLists.txt seems to not include search paths for sysroot/usr/include/soci one way you could do it is refer to soci files with namespace when using them in source code like #include soci/soci.h then it will automatically apply the default sysroot search paths to includedir and reach it. Alternative is that you can defile a .cmake file for soci and include that in soci recipe and then just find the module in your package’s CMakeLists.txt Ross soci-example.tar.bz2-- ___ 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] Header-Files of DEPEND recipe not found
Good day, I am using the soci recipe: https://github.com/openembedded/meta-openembedded/tree/9a5d25f2a717814f948b492b9c01c1ff0edb678d/meta-oe/recipes-support/soci soci is successfully being built when using the following dependency in my own recipe which relies on soci: DEPENDS = soci soci produces the following output: soci/3.2.2-r0/image/usr/include/soci/(Contains the header-files needed by my recipe) soci/3.2.2-r0/image/usr/lib Furthermore the following *.ipk are being created by soci: soci/3.2.2-r0/deploy-ipks/core2-32/soci_3.2.2-r0_core2-32.ipk soci/3.2.2-r0/deploy-ipks/core2-32/soci-dev_3.2.2-r0_core2-32.ipk soci/3.2.2-r0/deploy-ipks/core2-32/soci-dbg_3.2.2-r0_core2-32.ipk soci/3.2.2-r0/deploy-ipks/core2-32/soci-staticdev_3.2.2-r0_core2-32.ipk The package soci-dev seems to contain the header-files as well as the libraries that my recipe needs. However, when compiling my own recipe I get compiling errors (soci.h not found). I am 100% sure that I specified the correct paths. What might be wrong here? I thought using DEPENDS = soci should handle this? DEPENDS = soci-dev results in: ERROR: Nothing PROVIDES 'soci-dev' (but my-recipe.bb DEPENDS on or otherwise requires it) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Header-Files of DEPEND recipe not found
2015-08-10 13:16 GMT+02:00 Burton, Ross ross.bur...@intel.com: The first step would be to verify that the sysroot does in fact have the headers installed in Ross Thank you for your response! How do I verify that? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Header-Files of DEPEND recipe not found
Please see the attachment for a simplified example. A library (consisting of 1 cpp and 1 header) is being built using soci. Compiling fails since soci.h is not found. 2015-08-10 13:16 GMT+02:00 Burton, Ross ross.bur...@intel.com: On 10 August 2015 at 12:13, yocto yocto yoctomailingl...@gmail.com wrote: However, when compiling my own recipe I get compiling errors (soci.h not found). I am 100% sure that I specified the correct paths. The headers are likely installed in the sysroot, but your script can't find them. The first step would be to verify that the sysroot does in fact have the headers installed in, and then you'll have to debug your configure scripts to find out why they don't find the headers. Sharing your recipe and sources will help here. Ross soci-example.tar.bz2 Description: BZip2 compressed data -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Disable Warning: X, set to be excluded, is excluded [...]
I am building my own yocto image based on the intel edison image. For that reason i created my own layer so that I do not have to touch the official intel sources. Each change is done in my own layer. Hence, to remove packages that are added within the intel edison configuration I use PACKAGE_EXCLUDE in my own layer.conf. E.g.: PACKAGE_EXCLUDE = pwr-button-handler Result: Warning: Package pwr-button-handler, set to be excluded, is in myown-image PACKAGE_INSTALL (*here follows a list with all recipes included*). So this warning is 100% correct: I am removing a package which has been added before. But is it possible to avoid this warning? I only found this: PACKAGE_EXCLUDE is a mechanism for preventing packages from being installed at all. If the package is in the PACKAGE_INSTALL or ACKAGE_INSTALL_ATTEMPTONLY it will be filtered out, and a warning issued. (http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/41490) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] libmcrypt not part of the image
I added the meta-openembedded layer to my configuration. I want to have
libmcrypt (in meta-openembedded/meta-oe/recipes-support) on my system:
IMAGE_INSTALL += libmcrypt
The library (libmcrypt.so) is actually being built. Everything is located
in libmcrypt/2.5.8-r0/package/usr, however after flashing the image
libmcrypt is not part of the filesystem.
I tried writing some kind of libmcrypt_%.bbappend with
do_install() {
install -m 0755 ${WORKDIR}/package/usr ${D}/
}
However, I get a bitbake error that do_install failed but there is exact
message. Any ideas how to solve this properly?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] do_install_append_class-target(): Files are not being installed on the system
Good day, I am writing a recipe using inherit autotools. I am using do_install_append_class-target() to install all files on the system. The folder build/tmp/work/core2-32-poky-linux/my-recipe/x.y.z-r0/image contains all files respectively the desired folder structure. However, after flashing my image all folders and files are not there. What might be the problem? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to enable php5 (php_5.5.24.bb) support for postgresql
I am willed to do this since I rely on postgresql. It would help if you could provide some hints which files are or might be related to the problem since I am relatively new to yocto. I would do the rest of the work. 2015-05-28 13:15 GMT+02:00 Paul Eggleton paul.eggle...@linux.intel.com: On Saturday 23 May 2015 11:12:22 yocto yocto wrote: after looking at the config.log that I sent you I realized that all unsafe for cross-compilation message occur because the recipe tries to link against my local installation of postgresql-server-dev-9.3 and libpq-dev lying in /usr/lib. Consider the following line: skipping incompatible /usr/lib/libpq.so when searching for -lpq The recipe is doing right to skip the library, because I am using Ubuntu 64bit. Therefore my local installations of postgresql-server-dev-9.3 and libpq-dev are 64 bit versions. So yesterday evening/night I did the following: - I installed a virtual machine Ubuntu 32 bit - I downloaded the latest linux sources (edison-src-ww18-15-1.tgz) - I added the meta-openembbed layer (daisy branch) - I removed the php recipe from the daisy branch and replaced it by the latest from the master branch - I added PACKAGECONFIG_pn-php = mysql sqlite3 pgsql in local.conf - I added my own layer - I built the image Result: Everything builds fine from scratch beside the php recipe. I appended the latest config.log. As you can see some dependencies are missing resulting in linker errors and I still get the unsafe for cross-compilation error. Is the approach of the recipe correct (linking against local packages?). Certainly not. A recipe built for the target machine should never be picking up includes or libraries from the host, that's why this check exists. We need to ensure the configure script does not look at host locations at all. I guess one reason we haven't picked up on this is that by default postgres functionality is disabled. What is your system configuration? Do you have any ideas or do you know a person who might help? The system I did my most recent build on is a CentOS 6 machine, but that's probably not why it works for me - it likely works for me because I simply don't have postgres or its development files installed, so there's nothing for the configure script to find on the host. Unfortunately this is a case where someone is going to have to dig into the php configure script, find out how that -L/usr/lib is getting into the linker path, and then stop that from happening; depending on how it is getting in there that may be an additional argument to the configure script or it might require patching the configure.ac file. Using grep and a little knowledge of how autoconf works this shouldn't be too difficult, but it's not something I have time for at the moment. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to enable php5 (php_5.5.24.bb) support for postgresql
I set BBCLASSEXTEND = native active again. My php_5.5.24.bbappend looks like this (just one line): PACKAGECONFIG_append_class-native = pgsql However, the error still persists, nothing changed: - ERROR: Nothing PROVIDES 'postgresql-native' (but /recipes-devtools/php/ php_5.5.24.bb DEPENDS on or otherwise requires it). Close matches: postgresql strace-native popt-native NOTE: Runtime target 'php' is unbuildable, removing... Missing or unbuildable dependency chain was: ['php', 'php-native', 'postgresql-native'] ERROR: Required build target 'myImage-image' has no buildable providers. Missing or unbuildable dependency chain was: ['myImage-image', 'php', 'php-native', 'postgresql-native'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. - When changing php_5.5.24.bbappend to #PACKAGECONFIG_append_class-native = pgsql everything compiles but of course the support for pgsql is missing. I found this: https://www.yoctoproject.org/irc/%23yocto.2013-12-17.log.html But this discussion is not helping me (search for postgresql-native) 2015-05-22 13:17 GMT+02:00 Martin Jansa martin.ja...@gmail.com: On Fri, May 22, 2015 at 09:51:31AM +0100, Paul Eggleton wrote: On Thursday 21 May 2015 23:21:53 yocto yocto wrote: Good day, I am working with the intel Edison. Therefore I am using the meta-openembedded “daisy” branch (have a look here: https://github.com/openembedded/meta-openembedded/branches/stale). Using another branch causes bitbake errors. Beside this, “daisy” is recommended for the intel Edison within the official intel documents. Nevertheless I added apache2_2.4.9.bb and postgresql_9.2.4.bb to my custom image. However, php5 support is missing. Therefore I downloaded the php recipe from the current master branch and put it in my custom layer: https://github.com/openembedded/meta-openembedded/blob/b070899000162e7f4baf7 5e2427216b39c641a12/meta-oe/recipes-devtools/php/ https://github.com/openembedded/meta-openembedded/blob/b070899000162e7f4baf 75e2427216b39c641a12/meta-oe/recipes-devtools/php/ Furthermore I created “php_5.5.24.bbappend” with the following content in the same folder: PACKAGECONFIG_append += apache2 PACKAGECONFIG_append += pgsql bitbake php results in the following errors: ERROR: Nothing PROVIDES 'uw-imap' […] but php/php_5.5.24.bb DEPENDS on or otherwise requires it) ERROR: Required build target 'php' has no buildable providers. Missing or unbuildable dependency chain was: ['php', 'uw-imap'] So I removed the config “PACKAGECONFIG[imap]” from php_5.5.24.bb. Result: ERROR: Nothing PROVIDES 'postgresql-native' […] but /php/php_5.5.24.bb DEPENDS on or otherwise requires it). Close matches: postgresql strace-native popt-native ERROR: Required build target 'php' has no buildable providers. Missing or unbuildable dependency chain was: ['php', 'php-native', 'postgresql-native'] Google does not show much for postgresql-native related to yocto. bitbake postgresql is running fine... If I remove BBCLASSEXTEND = native from the recipe I get the following result: 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. The path was php/5.5.24-r0/php-5.5.24' ERROR: Function failed: do_qa_configure ERROR: Logfile of failure stored in: php/5.5.24-r0/temp/log.do_configure.22410 ERROR: Task 5 (php/php_5.5.24.bb, do_configure) failed with exit code '1' I appreciate any advice on how to set up php5 for postgresql. Change your PACKAGECONFIG_append lines in your bbappend to use PACKAGECONFIG_append_class-native instead and you should be able to progress. Also, you very likely shouldn't be removing the BBCLASSEXTEND. And add leading space in append instead of += (_append + += always looks wrong as the only function of += is to add the leading space), change it to: PACKAGECONFIG_append = pgsql Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to enable php5 (php_5.5.24.bb) support for postgresql
Thanks for helping me. My *.bbappend looks now like this:
PACKAGECONFIG_append_class-target = pgsql
bitbake php results now in:
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. The path was
'[...]/core2-32-poky-linux/php/5.5.24-r0/php-5.5.24'
ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
[...]/core2-32-poky-linux/php/5.5.24-r0/temp/log.do_configure.16729
ERROR: Task 5 ([...]/recipes-devtools/php/php_5.5.24.bb, do_configure)
failed with exit code '1
From the recipe I can see that
do_configure_prepend
do_configure_append
exist. For test purposes I added an empty
do_configure () {
}
This results in
ERROR: Function failed: do_install
(Much text)
cp: cannot stat 'ltmain.sh': No such file or directory
(Much text)
ERROR: oe_runmake failed
2015-05-22 14:48 GMT+02:00 Paul Eggleton paul.eggle...@linux.intel.com:
On Friday 22 May 2015 14:00:50 Martin Jansa wrote:
On Fri, May 22, 2015 at 01:44:20PM +0200, yocto yocto wrote:
I set BBCLASSEXTEND = native active again. My php_5.5.24.bbappend
looks
like this (just one line):
PACKAGECONFIG_append_class-native = pgsql
Do you really want to add it for native or target version?
Oops, yes, that was my mistake in my original reply - should be
class-target
not class-native.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to enable php5 (php_5.5.24.bb) support for postgresql
Please find the log file attached. The error is at the end
2015-05-22 15:38 GMT+02:00 Paul Eggleton paul.eggle...@linux.intel.com:
On Friday 22 May 2015 15:34:50 yocto yocto wrote:
Thanks for helping me. My *.bbappend looks now like this:
PACKAGECONFIG_append_class-target = pgsql
bitbake php results now in:
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. The path was
'[...]/core2-32-poky-linux/php/5.5.24-r0/php-5.5.24'
Can you please attach the full log.do_configure?
From the recipe I can see that
do_configure_prepend
do_configure_append
exist. For test purposes I added an empty
do_configure () {
}
This results in
ERROR: Function failed: do_install
(Much text)
cp: cannot stat 'ltmain.sh': No such file or directory
(Much text)
ERROR: oe_runmake failed
This is not an appropriate workaround - you can't just cut pieces of the
build
out like this.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
log.do_configure.18302
Description: Binary data
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to enable php5 (php_5.5.24.bb) support for postgresql
Good day, I am working with the intel Edison. Therefore I am using the meta-openembedded “daisy” branch (have a look here: https://github.com/openembedded/meta-openembedded/branches/stale). Using another branch causes bitbake errors. Beside this, “daisy” is recommended for the intel Edison within the official intel documents. Nevertheless I added apache2_2.4.9.bb and postgresql_9.2.4.bb to my custom image. However, php5 support is missing. Therefore I downloaded the php recipe from the current master branch and put it in my custom layer: https://github.com/openembedded/meta-openembedded/blob/b070899000162e7f4baf75e2427216b39c641a12/meta-oe/recipes-devtools/php/ https://github.com/openembedded/meta-openembedded/blob/b070899000162e7f4baf75e2427216b39c641a12/meta-oe/recipes-devtools/php/ Furthermore I created “php_5.5.24.bbappend” with the following content in the same folder: PACKAGECONFIG_append += apache2 PACKAGECONFIG_append += pgsql bitbake php results in the following errors: ERROR: Nothing PROVIDES 'uw-imap' […] but php/php_5.5.24.bb DEPENDS on or otherwise requires it) ERROR: Required build target 'php' has no buildable providers. Missing or unbuildable dependency chain was: ['php', 'uw-imap'] So I removed the config “PACKAGECONFIG[imap]” from php_5.5.24.bb. Result: ERROR: Nothing PROVIDES 'postgresql-native' […] but /php/php_5.5.24.bb DEPENDS on or otherwise requires it). Close matches: postgresql strace-native popt-native ERROR: Required build target 'php' has no buildable providers. Missing or unbuildable dependency chain was: ['php', 'php-native', 'postgresql-native'] Google does not show much for postgresql-native related to yocto. bitbake postgresql is running fine... If I remove BBCLASSEXTEND = native from the recipe I get the following result: 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. The path was php/5.5.24-r0/php-5.5.24' ERROR: Function failed: do_qa_configure ERROR: Logfile of failure stored in: php/5.5.24-r0/temp/log.do_configure.22410 ERROR: Task 5 (php/php_5.5.24.bb, do_configure) failed with exit code '1' I appreciate any advice on how to set up php5 for postgresql. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Intel Edison] Changing kernel configuration results in do_rootfs-failure (Code 255)
I tried to add a module to the kernel configuration according to
http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html#changing-the-configuration
Here is what I have done:
File:
meta-mylayer/recipes-kernel/linux/linux-yocto_3.10.bbappend
Contains:
FILESEXTRAPATHS_prepend := ${THISDIR}/files:
SRC_URI += file://FTDI.cfg
File:
meta-mylayer/recipes-kernel/linux/files/FTDI.cfg
Contains:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_FTDI_SIO=y
File:
meta-mylayer/recipes-mylayer/images/mylayer-image.bb
Contains:
IMAGE_INSTALL += \
linux-yocto \
[...]
Bitbake result:
ERROR: Unable to install packages. Command
'/home/ubuntu/development/edison-src/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl
-f
/home/ubuntu/development/edison-src/build/tmp/work/edison-poky-linux/geent-image/1.0-r0/opkg.conf
-o
/home/ubuntu/development/edison-src/build/tmp/work/edison-poky-linux/geent-image/1.0-r0/rootfs
--force_postinstall --prefer-arch-to-version install i2c-tools
run-postinsts nano useradd linux-yocto base-files postgresql
packagegroup-core-boot' returned 255:
[...]
Collected errors:
* opkg_install_cmd: Cannot install package linux-yocto.
[...]
ERROR: Function failed: do_rootfs
What might be wrong here?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
