> This is a known feature with the test suite, hence the FIP result > code, which is encountered on systems using shared libraries. > Upon performing the chroot() call > the shared library is no longer accessible and the process terminates. > The FIP code is not a failure but requires manual inspection. > We may want to look at changing the output/result code so > we can avoid the manual inspection .
Ought not the build procedure ensure that this test is not built with a reference to a shared library that won't be present in the chroot environment? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with subject of "unsubscribe". Trouble? Email [EMAIL PROTECTED]
