From: Mo DeJong <supermo@bayarea.net>
To: Insight <insight@sources.redhat.com>
Subject: Patch to avoid using mkfifo under Cygwin
Date: Thu, 12 Sep 2002 15:51:00 -0000 [thread overview]
Message-ID: <20020912155153.5df1e557.supermo@bayarea.net> (raw)
Here is a patch that avoids calling mkfifo under Cygwin since
it is not functional.
Mo
2002-09-12 Mo DeJong <supermo@bayarea.net>
* unix/tclUnixFCmd.c (DoCopyFile): Don't use mkfifo
when compiling with Cygwin, since it is not supported.
Index: unix/tclUnixFCmd.c
===================================================================
RCS file: /cvs/src/src/tcl/unix/tclUnixFCmd.c,v
retrieving revision 1.2
diff -u -r1.2 tclUnixFCmd.c
--- unix/tclUnixFCmd.c 9 Sep 2001 23:56:09 -0000 1.2
+++ unix/tclUnixFCmd.c 12 Sep 2002 22:37:10 -0000
@@ -391,12 +391,18 @@
}
return CopyFileAtts(src, dst, &srcStatBuf);
}
+#ifndef __CYGWIN__
+ /*
+ * mkfifo is not supported under Cygwin even though it is prototyped
+ * in newlib headers.
+ */
case S_IFIFO: {
if (mkfifo(dst, srcStatBuf.st_mode) < 0) { /* INTL: Native. */
return TCL_ERROR;
}
return CopyFileAtts(src, dst, &srcStatBuf);
}
+#endif /* __CYGWIN__ */
default: {
return CopyFile(src, dst, &srcStatBuf);
}
next reply other threads:[~2002-09-12 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 15:51 Mo DeJong [this message]
2002-09-12 16:06 ` Patch to avoid using mkfifo under cygwin Christopher Faylor
2002-09-13 7:44 ` Patch to avoid using mkfifo under Cygwin Keith Seitz
2002-09-13 9:39 ` Patch to avoid using mkfifo under cygwin Christopher Faylor
2002-09-13 9:57 ` Keith Seitz
2002-09-13 11:01 ` Mo DeJong
2002-09-13 11:05 ` Keith Seitz
2002-09-13 14:32 ` Christopher Faylor
2002-09-13 12:22 ` Patch to avoid using mkfifo under Cygwin Andrew Cagney
2002-09-17 10:27 Patch to avoid using mkfifo under cygwin Nicholas Wourms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020912155153.5df1e557.supermo@bayarea.net \
--to=supermo@bayarea.net \
--cc=insight@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).