Yocto SDK 1.3 Fails building fsl-image-lsb-sdk on p2041

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Yocto SDK 1.3 Fails building fsl-image-lsb-sdk on p2041

Jump to solution
4,507 Views
davidvanbeveren
Contributor I

Has anyone successfully built the fsl-image-lsb-sdk bitbake image using the 1.3 SDK?

I installed yocto from the 1.3 (20121114) SDK iso, on a fresh install of Ubuntu 12.04.2 LTS. Now I know that 12.04.1 (and 12.04) are explicitly supported and 12.04.2 is not explicitly supported, but this is not a platform problem as far as I can tell.

Bitbake notices an error during dependency checking at the beginning of the build:

NOTE: Preparing runqueue

ERROR: Multiple .bb files are due to be built which each provide udev (/home/dvb/QorIQ-SDK-V1.3-20121114-yocto/meta/recipes-core/udev/udev_164.bb /home/dvb/QorIQ-SDK-V1.3-20121114-yocto/meta-oe/meta-oe/recipes-core/udev/udev_182.bb).

This usually means one provides something the other doesn't and should.

This problem comes back to bite me during the build, as the 182 udev is needed (actually udev >=172) by the recipe systemd-git-r29.

checking for UDEV... no

| configure: error: Package requirements ( libudev >= 172 ) were not met:

|

| Requested 'libudev >= 172' but version of libudev is 164

|

| Consider adjusting the PKG_CONFIG_PATH environment variable if you

| installed software in a non-standard prefix.

|

| Alternatively, you may set the environment variables UDEV_CFLAGS

| and UDEV_LIBS to avoid the need to call pkg-config.

| See the pkg-config man page for more details.

| ERROR: oe_runconf failed

NOTE: package systemd-git-r29: task do_configure: Failed

What is the correct way to work around this problem?

Note that fsl-image-minimal builds correctly. I have not yet tested deploying it on a box but the build completed without error.

One other thing I noted was that the "distro" field output by Yocto at the beginning of the build is 1.2 not 1.3, though I may be confusing things here:

OE Build Configuration:

BB_VERSION        = "1.15.2"

TARGET_ARCH       = "powerpc"

TARGET_OS         = "linux"

MACHINE           = "p2041rdb"

DISTRO            = "fsl"

DISTRO_VERSION    = "1.2"

TUNE_FEATURES     = "m32 fpu-hard ppce500mc"

TARGET_FPU        = "hard"

meta             

meta-yocto        = "master:b936b3333997d36d401a9c6a9603af57fc88e842"

meta-fsl-ppc      = "master:0e12f1d72e778d98a0e2d7cf2c9df09b545d40d9"

meta-fsl-ppc-private = "(nobranch):4e71da366b990d4861c5f64fcf071152c8d2a32f"

meta-oe           = "master:4f9dd3e80eb59c7c73841c85a2a703b98566572c"

Tags (3)
1 Solution
1,997 Views
zhenhualuo
NXP Employee
NXP Employee

Regarding the build issue of fsl-image-lsb-sdk, you can try following workaround:

   1. edit meta-fsl-ppc/conf/machine/p2041rdb.conf to add PREFERRED_VERSION_udev="175"

    2. bitbake udev -c cleansstate

    3. bitbake fsl-image-lsb-sdk


The distro version is Yocto version instead of FSL SDK version, SDK 1.3 uses Yocto 1.2.

BTW, since fsl-image-lsb-sdk includes the packages of lsb standard, the rootfs image size is very large, and most packages are not necessary, fsl-image-core/fsl-image-full are recommended rootfs types.

View solution in original post

2 Replies
1,998 Views
zhenhualuo
NXP Employee
NXP Employee

Regarding the build issue of fsl-image-lsb-sdk, you can try following workaround:

   1. edit meta-fsl-ppc/conf/machine/p2041rdb.conf to add PREFERRED_VERSION_udev="175"

    2. bitbake udev -c cleansstate

    3. bitbake fsl-image-lsb-sdk


The distro version is Yocto version instead of FSL SDK version, SDK 1.3 uses Yocto 1.2.

BTW, since fsl-image-lsb-sdk includes the packages of lsb standard, the rootfs image size is very large, and most packages are not necessary, fsl-image-core/fsl-image-full are recommended rootfs types.

1,996 Views
davidvanbeveren
Contributor I

Thanks for the tip, it's building now and got past the udev breakage I saw

earlier. I'll mark this as answered as soon as the build completes.

On Fri, Mar 29, 2013 at 6:51 PM, Zhenhua Luo

0 Kudos
Reply