On 12-08-03 01:45 PM, Mark Hatle wrote:
On 8/3/12 11:44 AM, Yao Zhao wrote:
Hi all,
Any suggestion to fix these kinds of QA warnings?
libpam is referencing /usr/lib/libcrack from /lib/security.
I tried to fix cracklib to install to /lib but cracklib is using other
libraries from /usr/lib, I am afraid that I am touching a chain, so any
good ideas?
Historically I'm used to cracklib being in /lib... but I also don't
remember a huge chain of additional libraries.
libcrack is depending on libz and libz is in usr/lib too.
Seems libz didn't depend another.
What exactly reason that this is a serious problem? Is this a standard?
It is quite possible that a lib library depending on usr/lib then .....
Do we have a one-shot cure?
yao
It may be worth identifying the chain and seeing if we can break it,
or at least reduce it in some fairly easy way.
--Mark
thanks,
yao
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
