From: "Consequator" <Consequator@mad.scientist.com>
To: <cygwin@sourceware.cygnus.com>
Subject: gcc problem
Date: Fri, 11 Aug 2000 16:12:00 -0000 [thread overview]
Message-ID: <000501c003e9$99d04380$d520bbd4@chello.nl> (raw)
$ cpp -DFORK -DWIN32 darkbot.c -o darkbot -luser32
cpp: installation problem, cannot exec
`/usr/lib/gcc-lib/i686-cygwin/2.95.2/cpp.exe': Permission denied
can anyone tell me why its giving me this ?
it is giving me that msg when i do a make and showing a poppup window static
that cpp.exe is linked to an missing output cygwin1.dll:_ctype_.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-08-11 16:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 16:12 Consequator [this message]
2000-08-11 17:22 ` Chris Faylor
2000-08-12 3:37 ` Consequator
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 12:49 Lauer Rainer
2004-03-02 12:53 ` Laurent Vaucher
2004-03-02 14:56 ` Gerrit P. Haase
2004-03-02 15:57 ` Gareth Pearce
2003-09-14 21:00 swa004
2002-03-21 5:39 GCC problem Robert Collins
2002-03-21 5:17 Mike Hayden
2002-03-21 5:26 ` David Starks-Browning
[not found] <Pine.LNX.4.33.0112142057150.7431-100000@heros.knurow.tpsa. pl>
2001-12-14 11:41 ` Larry Hall (RFK Partners, Inc)
2001-12-14 11:11 gahan
2001-09-06 7:31 gcc problem Peter Buckley
2001-09-06 7:36 ` Larry Hall (RFK Partners, Inc)
2001-09-06 6:45 Peter Buckley
2001-09-06 7:17 ` Dominik Zalewski
2001-09-06 6:41 Dominik Zalewski
2001-07-27 10:14 gcc_Problem Mr.Serkan Gumusbicak
2001-07-27 11:50 ` gcc_Problem Carl Hetherington
1997-10-23 7:26 gcc problem Frank Packenham
1997-10-20 19:25 Colin Peters
1997-10-21 7:44 ` Steven J. Zeil
1997-10-20 3:21 Frank Packenham
1997-10-20 6:00 ` Fergus Henderson
1997-03-10 4:11 Jon Thackray
1997-03-10 6:04 ` Jim Balter
1997-03-10 6:11 ` Jon Thackray
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='000501c003e9$99d04380$d520bbd4@chello.nl' \
--to=consequator@mad.scientist.com \
--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).