On Tue, Nov 27, 2007 at 10:16:43AM +0100, Rafael Garcia-Suarez wrote: > On 26/11/2007, Matt Kraai <kraai@ftbfs.org> wrote: > > Howdy, > > > > According to fpathconf's manual page on GNU/Linux, > > > > > If the system does not have a limit for the requested resource, -1 > > > is returned, and errno is unchanged. > > > > According to the documentation on QNX, > > > > > Returns: > > > > > > The requested configurable limit, or -1 if an error occurred (errno > > > is set). > > > > > > Errors: > > > > > > EINVAL > > > The name argument is invalid, or the indicated limit isn't > > > supported for this filedes. > > > > In practice, it appears to set errno to ENOSYS if the indicated limit > > isn't supported for this filedes. > > > > ext/POSIX/t/sysconf.t appears to expect the GNU/Linux behavior, so it > > fails on QNX. Should the test case be modified so that it doesn't > > fail on QNX? If so, how? > > Thanks for the feedback. > You should modify the test so it checks the value of $^O and is > skipped in the QNX case. (Since apparently the QNX behaviour doesn't > match what is documented, it's probably better not to test it > explicitly.) I've attached a patch that does so. > (What's the value of $^O on QNX ?) nto -- MattThread Previous | Thread Next