[bind10-dev] unit tests and /usr/local

[JINMEI Tatuya / 神明達哉]

At Mon, 22 Mar 2010 09:31:38 -0500 (CDT),
"Jeremy C. Reed" <jreed at isc.org> wrote:
> 
> See recent FreeBSD7-amd64 "unittests" at
> http://bind10.isc.org/~tester/builder/builder.html

> Making check in tests
> make  check-TESTS
> /libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 
> required by /usr/local/lib/libcfgclient.so.0 not found

> I haven't looked closely yet. This is on jinmei-1.lab and I think the 
> above installation to /usr/local/ got installed early Friday morning 
> (when I was a sleep).

Hmm, apparently I installed objects built with g++ 4.4 in a
system-standard directory (i.e. /usr/local/lib) as a result of
misoperation.  I needed to use g++4.4 to enable python binding, and to
confirm the behavior I installed (or intended to install) the binaries
under "/opt/local".  But probably I forgot to specify --prefix in one
of the attempts.

I simply removed them (with other binaries/executables that were
mistakenly installed under /usr/local), so the test by the bot should
be fine now.

But...

> Any ideas on how to get the unittest to not link with outside libraries?

...this type of confusion could happen even if it's not a mistake.
So, as already suggested in this thread, I think it's safer to
explicitly specify LD_LIBRARY_PATH in the test environment so that the
binaries being tested are always preferred.

---
JINMEI, Tatuya