From: David Billinghurst <dbcygwin@gmail.com>
To: cygwin@cygwin.com
Subject: access() function in 1.7
Date: Sat, 24 Jan 2009 09:14:00 -0000 [thread overview]
Message-ID: <497AC602.6050709@gmail.com> (raw)
I am having a problem with the access() function in cygwin-1.7.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38956
$ touch foobar_file
$ chmod a-w foobar_file
$ cat test_access.c
#include <stdio.h>
#include <unistd.h>
int main (void) {
char *file="foobar_file";
int m = W_OK;
printf("access = %d\n",access(file,m));
}
$ touch foobar_file
$ chmod a-w foobar_file
Under cygwin-1.5
$ ./test_access
access = -1
Under cygwin-1.7
$ ./test_access.exe
access = -1
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2009-01-24 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 9:14 David Billinghurst [this message]
2009-01-24 21:27 ` Corinna Vinschen
2009-01-24 22:55 ` David Billinghurst
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=497AC602.6050709@gmail.com \
--to=dbcygwin@gmail.com \
--cc=cygwin@cygwin.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).