Re: T.chroot 4
If we have enough in the LSB specification to do this portably, then yes
it should be changed.
On Mar 29, 11:12am in "Re: T.chroot 4", Joey Hess wrote:
> Andrew Josey wrote:
> > 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 .
> Ok. I wonder why you don't just link the test program statically?
To UNSUBSCRIBE, email to email@example.com
with subject of "unsubscribe". Trouble? Email firstname.lastname@example.org