bitbake build fails with php and mariadb - libmysqlclient

Hi experts,

I finally managed to get bitbake running to make the image for iot2000-example :-)

Now I want to include nginx, mariadb and php to my image.
Nginx and mariadb are running well, but there is an issue with the libmysql included in php.

After starting php (or php-fpm) I do get the following error:

version libmysqlclient_16 not defined in file libmysqlclient.so.18 with link time reference

It looks like in yocto krogoth the libs mariadb and php don't work very well together.

Unfortunately I don't know how to solve this.
The only hint I did found was an old IRC chat where this issue came up bit there was no answer to that question :-(

see here: http://logs.nslu2-linux.org/livelogs/oe/oe.20160707.txt

What can I do?
The newer version of yocto (2.2) does not work with iot2000

It should be possible to get Yocto 2.2 running when removing the 2.1-only packages from the build (PACKAGE_EXCLUDE) and updating all dependencies to their morty branches.

The meta-iot2000-bsp layer was reported to build even against master branches of Yocto and other required layers. For meta-iot2000-example, at least the Arduino support would have to be removed (galileo-target).

I did set up a new toolchain with yocot2.2.

But I'm not able to compile even only the bsp image.

I do get  errors at the potgresql recipe and during config pci and config vga.

How can I disable postgresql and the pci and vga console because I don't need them anyway?

I'm really disappointed bacause I'm now trying for weeks to compile an image with webserver, php and mysql (mariadb). This is nothing fancy and should be very standard.

I have experince with yocto to build images for phytec boards and there everything runs like a charm with the newest yocto version and meta-openembedded recipes.

We are carrying some baggage with what we inherited from the reference board, its BSP and ecosystem. Cleaning this up is work in progress but takes some time. Meanwhile, the latest-and-greatest is unfortunately not in the test loop.

However, I can try to reproduce what you did later today if you can share your local.conf and bblayers.conf (ideally in their simplest non-working form). Please also tell me which revisions (hashes) of the target layers you checked out.

Many thanks.

Here is the info:

The hashes are the same as described in the readme.md of iot2000-bsp and iot2000-example at github.

Build Configuration:

BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "iot2000"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1"
TUNE_FEATURES     = "m32 i586-nlp"
TARGET_FPU        = ""
meta
meta-poky
meta-yocto-bsp    = "HEAD:6c1c01392d91f512e2949ad1d57a75a8077478ba"
meta-oe
meta-networking
meta-python
meta-webserver
meta-multimedia
meta-ruby         = "HEAD:247b1267bbe95719cd4877d2d3cfbaf2a2f4865a"
meta-intel        = "HEAD:9a06fc5bce051c47816d139184753ecdcc29987c"
meta-java         = "HEAD:9edf7d5aa5bdcf9afc4365fd1d85feca72b4ef1a"
meta-intel-iot-middleware = "HEAD:821cf14c8304669d9ce0c5b87b9be5a6eecff6e5"
meta-iot2000-bsp
meta-iot2000-example = "master:d8990d123643c6fc67c1fb0d9349295a124dfd7e"

Content of bblayers.inc

POKY_BBLAYERS_CONF_VERSION = "2"

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

BBLAYERS ?= " \
/home/siemensiot/yocto21/poky/meta \
/home/siemensiot/yocto21/poky/meta-poky \
/home/siemensiot/yocto21/poky/meta-yocto-bsp \
/home/siemensiot/yocto21/poky/meta-oe/meta-oe \
/home/siemensiot/yocto21/poky/meta-oe/meta-networking \
/home/siemensiot/yocto21/poky/meta-oe/meta-python \
/home/siemensiot/yocto21/poky/meta-oe/meta-webserver \
/home/siemensiot/yocto21/poky/meta-oe/meta-multimedia \
/home/siemensiot/yocto21/poky/meta-oe/meta-ruby \
/home/siemensiot/yocto21/poky/meta-intel \
/home/siemensiot/yocto21/poky/meta-java \
/home/siemensiot/yocto21/poky/meta-intel-iot-middleware \
/home/siemensiot/yocto21/poky/meta-iot2000/meta-iot2000-bsp \
/home/siemensiot/yocto21/poky/meta-iot2000/meta-iot2000-example \
"

at the end of local.conf I did insert the line

IMAGE_INSTALL_append = " php php-cli mariadb"

I did exclude node-red because this did cause a bunch of errors (and I don't need it).
So I commented out the following line at
poky/meta-iot2000/meta-iot2000-example/recipes-core/images/iot2000-example-image.inc

# IMAGE_INSTALL_append = " node-red node-red-dashboard node-mraa node-red-node-intel-gpio"

This all compiles without any errors.

Then I go to the serial console and do:

iot2000 login: root
root@iot2000:~# php -v
php: relocation error: php: symbol mysql_server_init, version libmysqlclient_16 not defined in file libmysqlclient.so.18 with link time reference

This shows the error from php.

First of all, meta-iot2000-bsp builds fine against yocto 2.2, I was able to confirm this. But meta-iot2000-example or its dependent layers still have problems beyond the galileo-target packages and its dependencies which I couldn't resolve quickly.

But your issue may be simpler to fix: A colleague pointed to https://sourceware.org/bugzilla/show_bug.cgi?id=19698, and that bug is only addressed in yocto 2.1.2. So please update your 2.1 build and try again.

Many thanks.
I did update to yocto 2.1.2 (with git -C checkout yocto-2.1.2)
But now I'm running into issues with e2fsprogs. This does not compile!

The recipes are the same as before, wehere I could build the image (but PHP did not work).

The errors are:

 ERROR: e2fsprogs-1.42.99+1.43+gitAUTOINC+0f26747167-r0 do_compile: oe_runmake failed

/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_git.bb, do_compile) failed with exit code '1'

This builds for me:

Build Configuration:
BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "openSUSEproject-13.2"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "iot2000"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1.2"
TUNE_FEATURES     = "m32 i586-nlp"
TARGET_FPU        = ""
meta
meta-poky
meta-yocto-bsp    = "HEAD:cca8dd15c8096626052f6d8d25ff1e9a606104a3"
meta-intel        = "patches:1b1d31fbe52a521ae71fba2c64b55e4648e649fb"
meta-iot2000-bsp
meta-iot2000-example = "master:d8990d123643c6fc67c1fb0d9349295a124dfd7e"
meta-oe           = "krogoth:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-java         = "master:a265b31ec7d022be254abdf959360a7624208585"
meta-intel-iot-middleware = "master:fc8eabfa4fb54802d3f97123b9d2954450175e33"

(meta-intel is locally patched due to an unrelated upstream issue)

With

IMAGE_INSTALL_remove = "node-red"
IMAGE_INSTALL_append = " php php-cli mariadb"

in local.conf (the node-red recipe is broken ATM, likely due to floating npm references - I've informed the developer). Then I get an image with php that runs on the IOT2000.

If this doesn't work, maybe you need to clean your build tmp first, or even the sstate-cache.