Machine specific packages lacking shlibs

Machine specific packages lacking shlibs

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm building various packages that statically link to libraries that
have too much knowledge about the kernel, so I have to make them machine
specific. But after doing so all the shared libs have disappeared from
the Depends: field!

Does anyone have some hints where this should get fixed?


regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLmRYHMkyGM64RGpERAmzfAKCj97/lRBX5HNXjmD+O4Mt92ij63QCfeqZW
LAEEFBmh01oHP9JEEXZnVwU=
=nsB7
-----END PGP SIGNATURE-----

Re: Machine specific packages lacking shlibs

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-03-10 17:10, Koen Kooi wrote:
> Hi,
> 
> I'm building various packages that statically link to libraries that
> have too much knowledge about the kernel, so I have to make them machine
> specific. But after doing so all the shared libs have disappeared from
> the Depends: field!
> 
> Does anyone have some hints where this should get fixed?

OK, some digging into package.bbclass shows that SHLIBS dir is pointing
to machinespecific staging. That's cause by the recipe changing
BASEPKG_HOST_SYS to get it to stage its libs into machinespecific
staging where they belong. So:

If you poke at PASEPKG_HOST_SYS, also poke at SHLIBSDIR.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLmR2vMkyGM64RGpERAsK+AJ0fjdoDXpTCG3D08vUkUGmqJ101PACguCnY
VKUMRg3+ebRFgdcx6vgJQP8=
=lprG
-----END PGP SIGNATURE-----