This is the mail archive of the
mailing list for the Cygwin project.
Re: not updating unwritable cache ../config.cache
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: not updating unwritable cache ../config.cache
- From: Glenn Spell <glenn at gs dot fay dot nc dot us>
- Date: Tue, 5 Oct 1999 05:29:57 -0400
- Organization: the aerie
- References: <E11YQRUfirstname.lastname@example.org>
On 5 Oct 1999 around 10:59AM (+0200) Kai Henningsen wrote:
> On 5 Oct 99, at 10:15, I wrote:
> > I'm seeing this every time I ./configure something. Anybody know
> > what is going on?
> > Sure doesn't _look_ unwritable. Besides, the very same script
> > just created it.
It's unwritable by anyone other the owner of the file.
> Well, it's "test -w" failing. Obviously because of this:
> bash-2.02$ id
> uid=1000(kai) gid=513(Kein) groups=513(Kein)
> bash-2.02$ chmod a+w test
If you're using a recent snapshot, setting "ntsec" in your CYGWIN
variable may cause chmod to work correctly. (I say "may" because I
really don't know. I don't run NT.) Historically, chmod returns
without error on Cygwin but does nothing.
> bash-2.02$ ls -la test
> -rw-r--r-- 1 544 Kein 0 Oct 5 09:57 test
You (UID 1000) don't own the file, UID 544 (administrator) owns
it. (I guess you already knew that. :-)
You need to login as administrator or wait for someone else to
provide information on how to enable ntsec and Unix permissions.
________________________________________ _ _____
) )_ _ (__\____o /_/_ |
) Glenn Spell <email@example.com> ) >-----._/_/__]>
)________________________________________) `0 |
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org