From: N8TM@aol.com
To: oskarb@fagorautomation.es, cygwin@sourceware.cygnus.com
Subject: Re: [B20.1]: Permission denied, sometimes
Date: Thu, 04 Mar 1999 22:01:00 -0000 [thread overview]
Message-ID: <84100e93.36df72a0@aol.com> (raw)
In a message dated 3/4/99 6:43:53 AM Pacific Standard Time,
oskarb@fagorautomation.es writes:
<< Moreover, gcc prints out, now and then, "Permission denied" errors
for the following file (?):
\usr\include\. >>
I've always found it necessary to symlink the appropriate directories to
/usr/include on W95. Apparently, that is the one place where #include files
may be found when all else fails.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: N8TM@aol.com
To: oskarb@fagorautomation.es, cygwin@sourceware.cygnus.com
Subject: Re: [B20.1]: Permission denied, sometimes
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <84100e93.36df72a0@aol.com> (raw)
Message-ID: <19990331194500.Trs5RSpa57wRFR4MQfGOtkc1NTF-TwI9w2OBlMLMbE8@z> (raw)
In a message dated 3/4/99 6:43:53 AM Pacific Standard Time,
oskarb@fagorautomation.es writes:
<< Moreover, gcc prints out, now and then, "Permission denied" errors
for the following file (?):
\usr\include\. >>
I've always found it necessary to symlink the appropriate directories to
/usr/include on W95. Apparently, that is the one place where #include files
may be found when all else fails.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-03-04 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-04 22:01 N8TM [this message]
1999-03-31 19:45 ` N8TM
-- strict thread matches above, loose matches on Subject: below --
1999-03-04 6:39 OSKAR BERRETEAGA
1999-03-31 19:45 ` OSKAR BERRETEAGA
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=84100e93.36df72a0@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=oskarb@fagorautomation.es \
/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).