From: "Kai Henningsen" <kai@cats.ms>
To: cygwin@sourceware.cygnus.com
Subject: not updating unwritable cache ../config.cache
Date: Tue, 05 Oct 1999 01:24:00 -0000 [thread overview]
Message-ID: <E11YPlz-0004zd-00@charlotte.intern.cats.ms> (raw)
I'm seeing this every time I ./configure something. Anybody know
what is going on?
bash-2.02$ find . -name "*cach*" -ls
363270609 0 -rw-r--r-- 1 544 Kein 0 Oct 04 14:11 ./config.cache
bash-2.02$
Sure doesn't _look_ unwritable. Besides, the very same script just
created it.
Regards - Kai Henningsen
--
http://www.cats.ms
Spuentrup CTI Fon: +49 251 322311 0
Windbreede 12 Fax: +49 251 322311 99
D-48157 Münster Mob: +49 161 3223111
Germany GSM: +49 171 7755060
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: "Kai Henningsen" <kai@cats.ms>
To: cygwin@sourceware.cygnus.com
Subject: not updating unwritable cache ../config.cache
Date: Sun, 31 Oct 1999 19:54:00 -0000 [thread overview]
Message-ID: <E11YPlz-0004zd-00@charlotte.intern.cats.ms> (raw)
Message-ID: <19991031195400.lL8wtv-eOIpIt16V_cnMk_apPkE6FkpN2awilcbwdgk@z> (raw)
I'm seeing this every time I ./configure something. Anybody know
what is going on?
bash-2.02$ find . -name "*cach*" -ls
363270609 0 -rw-r--r-- 1 544 Kein 0 Oct 04 14:11 ./config.cache
bash-2.02$
Sure doesn't _look_ unwritable. Besides, the very same script just
created it.
Regards - Kai Henningsen
--
http://www.cats.ms
Spuentrup CTI Fon: +49 251 322311 0
Windbreede 12 Fax: +49 251 322311 99
D-48157 Münster Mob: +49 161 3223111
Germany GSM: +49 171 7755060
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-10-05 1:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-05 1:24 Kai Henningsen [this message]
1999-10-31 19:54 ` Kai Henningsen
1999-10-05 2:07 Kai Henningsen
1999-10-05 2:30 ` Glenn Spell
1999-10-05 2:54 ` Kai Henningsen
1999-10-31 19:54 ` Kai Henningsen
1999-10-31 19:54 ` Glenn Spell
1999-10-31 19:54 ` Kai Henningsen
1999-10-05 5:12 Earnie Boyd
1999-10-05 5:43 ` Corinna Vinschen
1999-10-05 8:24 ` Kai Henningsen
1999-10-05 11:54 ` Corinna Vinschen
1999-10-06 1:55 ` Kai Henningsen
1999-10-06 8:05 ` Corinna Vinschen
1999-10-31 19:54 ` Corinna Vinschen
1999-10-31 19:54 ` Kai Henningsen
1999-10-06 3:24 ` Kai Henningsen
1999-10-06 8:05 ` Corinna Vinschen
1999-10-07 1:37 ` Kai Henningsen
1999-10-31 19:54 ` Kai Henningsen
1999-10-31 19:54 ` Corinna Vinschen
1999-10-31 19:54 ` Kai Henningsen
1999-10-31 19:54 ` Corinna Vinschen
1999-10-31 19:54 ` Kai Henningsen
1999-10-31 19:54 ` Corinna Vinschen
1999-10-31 19:54 ` Earnie Boyd
[not found] <E11YmB6-0007yR-00@charlotte.intern.cats.ms>
1999-10-06 8:49 ` Charles S. Wilson
1999-10-07 2:10 ` Kai Henningsen
1999-10-31 19:54 ` Kai Henningsen
1999-10-31 19:54 ` Charles S. Wilson
1999-10-07 2:54 Bernard Dautrevaux
1999-10-07 6:40 ` Kai Henningsen
1999-10-31 19:54 ` Kai Henningsen
1999-10-31 19:54 ` Bernard Dautrevaux
1999-10-07 4:42 Earnie Boyd
1999-10-31 19:54 ` Earnie Boyd
1999-10-07 5:05 Bernard Dautrevaux
1999-10-31 19:54 ` Bernard Dautrevaux
2000-03-24 13:07 John Wiersba
2000-03-24 13:36 ` John Fortin
2000-03-24 14:48 ` Larry Hall (RFK Partners, Inc)
2000-03-24 15:15 John Wiersba
2000-03-24 15:25 John Wiersba
2000-03-25 20:02 ` Larry Hall (RFK Partners, Inc)
2000-03-24 15:58 John Wiersba
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=E11YPlz-0004zd-00@charlotte.intern.cats.ms \
--to=kai@cats.ms \
--cc=cygwin@sourceware.cygnus.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).