Compile fmc (Frame Manager Configuration tool) into windriver linux image

[Tao2022]

Hi,

   I am trying to add fmc (Frame Manager Configuration tool) into my Windriver Linux image built for ls1043a. The recipe file already exists at QorIQ layer (WindRiver/layers/meta-freescale/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/fmc_git.bb). I add following line to my image bbappend file: 
PACKAGE_INSTALL:append = " fmc"

Then I am getting following compile error:
---------------------------------------

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'lib32-fmc' (but virtual:multilib:lib32: bitbake_build/../src/meta/meta-core/recipes-image/images/image-rescue.bb RDEPENDS on or otherwise requires it)
lib32-fmc was skipped: You are about to enable third-party components, there is additional third-part licensing involved, and you might need to consult with your legal department.

NOTE: Runtime target 'lib32-fmc' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['lib32-fmc']
ERROR: Required build target 'csrp' has no buildable providers.
Missing or unbuildable dependency chain was: ['csrp', 'lib32-image-rescue', 'lib32-fmc']

Summary: There were 2 ERROR messages, returning a non-zero exit code.
-----------------------------------------------------------------------

My question would be:
1) is this caused by improper bb file or bbapend file? or is it caused by not enabling the 3rd-party component (fmc)?

2) How do I fix it in either way?

I have spent couple of days on this, tried lot of things, but none works. Any hint of pointing of direction will be deeply appreciated.

[Tao2022 · Accepted solution]

I found the solution, post it here in case someone has similar issue like I did.

To add fmc into your image, add following lines to you yocto/local.conf:

CUSTOMER_RECIPES:freescale-layer += 'fmc'

CUSTOMER_RECIPES:freescale-layer += 'fmlib'

CUSTOMER_RECIPES:freescale-layer += 'tclap'

[yipingwang]

LS1043A is ARM64 architecture, in your build it is searching for 32 bit libs. It seems that there is problem with your recipes.

Is your Yocto SDK provided by Windriver? If yes, please contact Windriver to fix this problem.

[Tao2022]

Right, I thought it's the recipe issue as well. But if I copied the fmc recipes (include its support library fmlib) to higher layer (my meta layer), the build will pass and add fmc to /usr/bin. So it seems the recipes are fine.

[yipingwang]

It seems the error is caused by recipe image-rescue.bb which comes from WindRiver, please ask them to fix this problem.

[Tao2022]

No, image-rescue.bb is my own recipe file to add fmc into my kernel image. I should have nothing to do with fmc.
To make it simple, I just run "./bitbake fmc", then I get following error

ERROR: Nothing PROVIDES 'fmc'
fmc was skipped: You are about to enable third-party compnents, this is additional third-part licensing involved....

[yipingwang]

The problem is caused by your build option "virtual:multilib:lib32:", which makes fmc building as a 32bit lib. It should be built as a ARM 64bit binary.

[yipingwang]

Thanks for your information.