From: "Max Bowsher" <maxb@ukf.net>
To: "jblazi" <jblazi@gmx.de>, <cygwin@cygwin.com>
Subject: Re: Cannot compile my first Cygwin program
Date: Wed, 30 Oct 2002 01:38:00 -0000 [thread overview]
Message-ID: <000d01c27fe9$9ba9f6f0$78d96f83@pomello> (raw)
In-Reply-To: <200210300820.31545.jblazi@gmx.de>
jblazi <jblazi@gmx.de> wrote:
> Thank you for your help.
No problem.
>> The -I option shouldn't be needed at all.
>
> I saw that there is no such thing in the Cygwin examples. I suspect
> that I should set some variables manually. But which ones?
None.
>> *Backslash paths* !?!?! From *Cygwin* gcc? Could you have some other
>> gcc on your Windows system?
>
> I do not understand what you mean. It plays absolutely no rôle
> whether I use \cygwin... or /cygwin...
The error messages you posted showed backslashes in the error messages.
Cygwin gcc prints forward-slash paths in its error messages.
>> Run the command "gcc -v" and post the output.
>
> Here is the output:
>
> d:\cygwin\home\Administrator\c-programme>gcc -v
> gcc -v
> Using builtin specs.
> gcc version 2.95 19990728 (release)
Right - This version of gcc is either not from Cygwin at all, or is truly
ancient.
You should probably remove your Cygwin install and install the latest
version.
>> So / = d:\cygwin, but you don't want the -I option anyway.
>
> If I do not specify -I then the include path is not found and I get
> an error message.
This indicates that your installation is broken, not that you are supposed
to supply a command line option.
Max.
PS: Please keep replies on cygwin@cygwin.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-10-30 7:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 15:40 Elfyn McBratney
2002-10-29 17:23 ` jblazi
2002-10-29 20:13 ` Max Bowsher
[not found] ` <200210300820.31545.jblazi@gmx.de>
2002-10-30 1:38 ` Max Bowsher [this message]
2002-10-30 2:59 ` jblazi
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 3:44 Max Bowsher
2002-10-30 5:24 ` Janos Blazi
2002-10-30 6:54 ` David Starks-Browning
2002-10-29 20:47 Dockeen
2002-10-29 15:25 jblazi
2002-10-29 15:37 ` Max Bowsher
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='000d01c27fe9$9ba9f6f0$78d96f83@pomello' \
--to=maxb@ukf.net \
--cc=cygwin@cygwin.com \
--cc=jblazi@gmx.de \
/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).