Re: Enable linknamespace testing for libdl and libcrypt

[Joseph Myers <joseph at codesourcery dot com>]

On Thu, 17 Nov 2016, Florian Weimer wrote:

> Understood.  Then the linknamespace test fails thusly:
> 
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOWHASH_Begin
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOWHASH_Destroy
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOWHASH_End
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOWHASH_NewContext
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOWHASH_Update
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOW_Init
> [initial] crypt -> [libcrypt.a(crypt-entry.o)] __md5_crypt ->
> [libcrypt.a(md5-crypt.o)] NSSLOW_Shutdown
> 
> This is, of course, completely correct and expected.  I don't know what to do
> about it.  XFAIL it?

Assuming there are no implementation-namespace exports of those functions 
that libcrypt could use instead, that indicates whitelisting in 
linknamespace.pl with a comment referencing a bug filed for nss-crypt 
namespace issues.

-- 
Joseph S. Myers
joseph@codesourcery.com