On Fri, 18 May 2001, Adye, TJ (Tim) wrote:
> > Theoretically it should be possible to fix this becaue the
> > configure script detects POSIX compliance as not being available.
>
> That's a good point. I notice that configure already checks for mkfifo.
> Wouldn't it be best to disable the compilation of FvwmCommand if this check
> fails
Yes. This is what I meant originally.
(I assume this doesn't happen now)? With the dummy mkfifo in the new
> Cygwin, the configure check passes, so we'd still get a broken FvwmCommand -
Out of curiosity does the dummy mkfifo pass the POSIX compliance test?
I would assume not. Hence there should also be a way for the configure
script to check whether or not mkfifo works. How much of FvwmCommand
works without mkfifo? Is it possible to code an alternative version of
mkfifo that would work with cygwin using some trick? The alternative
version would then be compiled in conditionally.
> but at least then the build would work in all these cases.
Yes, this would be good.
Thanks,
Neil
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri May 18 2001 - 16:30:15 BST