In the past, I gave myself a lot of pain from trying to investigate the tests in nss - at that time I concluded that both nspr and nss needed to be built together for the tests to be meaningful, so in the book I've written:
| The testsuite is designed for testing changes to nss or nspr and is | not particularly useful for checking a released version (e.g. it | needs to be run on a non-optimized build with both nss and nspr | directories existing alongside each other). For further details, see | the User Notes. But when I was updating to nss-3.48 on my laptop the other night I noticed a gtest process kept appearing in 'top'. I suppsoe that's one of hte benefits of a slow machine. Looking at a log, I see it building infrastructure (libs and then gtests.o) followed by compiling many *_unittest.o objects from corresponding unittest.cc files and eventually it compiles sysinit_gtest. I think this means that tests are now run automatically during the build of nss. Opinions ? ĸen -- The right of the people to keep and arm Bears, shall not be infringed. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
