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

[Nathanael Hoyle]

On Mon, 2010-03-22 at 10:31, Jeremy C. Reed wrote:
> See recent FreeBSD7-amd64 "unittests" at
> http://bind10.isc.org/~tester/builder/builder.html
> 
> Making check in config
> Making check in .
> make  check-TESTS
> ==================
> All 0 tests passed
> ==================
> 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
> FAIL: run_unittests
> ====================================
> 1 of 1 test failed
> Please report to bind10-bugs at isc.org
> ====================================
> *** Error code 1
> 
> Stop in 
> 
> /usr/home/jreed/builder/work/BIND10/20100321033001-FreeBSD7-amd64/build/src/lib/config/tests.
> 
> 
> Notice how the unittest framework is using 
> /usr/local/lib/libcfgclient.so.0 versus the same library that was built 
> and exists in:
> 
> > ls 
> /usr/home/jreed/builder/work/BIND10/20100321033001-FreeBSD7-amd64/build/src/lib/config/.libs/
> ccsession.o             libcfgclient.la         libcfgclient.so.0
> config_data.o           libcfgclient.lai        module_spec.o
> libcfgclient.a          libcfgclient.so
> 
> 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).
> 
> Any ideas on how to get the unittest to not link with outside libraries?

Generally speaking, if you want dynamically linked libraries to be
resolved in a location other than the system default, you should set and
export LD_LIBRARY_PATH in your environment. If you want to ensure that
regardless of what the target system has for configuration, a given
specific library is used, you may need to consider static linking. I
hope I'm understanding your question correctly.

-Nathanael