ldconfig(8) oddity on 11.2-BETA3?

[Jonathan Chen]

Hi,

I'm running 11.2-BETA3/amd64 at r334236, and I've noticed that
"ldconfig -m" doesn't behave as expected (or perhaps it's my
understanding).

This is what I'm seeing when building security/nss in a chrooted environment:

# ldconfig -r | grep nss
# ls /usr/local/lib/nss
libcrmf.a               libnss3.so              libnssutil3.so
 libssl3.so
libfreebl3.so           libnssckbi.so           libsmime3.so
libfreeblpriv3.so       libnssdbm3.so           libsoftokn3.so
# ldconfig -m /usr/local/lib/nss
# ldconfig -r | grep nss
        search directories:
/lib:/usr/lib:/usr/local/lib:/usr/local/lib/perl5/5.26/mach/CORE:/usr/local/lib/nss
# ldconfig -R | grep nss
# ldconfig -r | grep nss
        search directories:
/lib:/usr/lib:/usr/local/lib:/usr/local/lib/perl5/5.26/mach/CORE:/usr/local/lib/nss
# file /usr/local/lib/nss/*.so
/usr/local/lib/nss/libfreebl3.so:     ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libfreeblpriv3.so: ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libnss3.so:        ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libnssckbi.so:     ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libnssdbm3.so:     ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libnssutil3.so:    ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libsmime3.so:      ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libsoftokn3.so:    ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
/usr/local/lib/nss/libssl3.so:        ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped

Is this correct ldconfig behaviour or has something broken?

Cheers.
-- 
Jonathan Chen <jonc at chen.org.nz>