From: Eliot Moss <moss@cs.umass.edu>
To: ASSI <Stromeko@nexgo.de>, cygwin@cygwin.com
Subject: Re: No such file or directory
Date: Mon, 6 Jul 2020 12:59:13 -0400 [thread overview]
Message-ID: <09da43ec-3235-dc9a-580a-916bc95616a9@cs.umass.edu> (raw)
In-Reply-To: <87pn98ppeg.fsf@Otto.invalid>
On 7/6/2020 12:41 PM, ASSI wrote:
> Billie Healy via Cygwin writes:
>> I downloaded Cygwin for use in a C programming class. I made sure to also
>> include gcc, make, nano, and vim. Nano and Vim do fine, but when I enter
>> gcc hello.c
>> bash reponds "no such file or directory."
>
> It would help if you posted the actual command line and response on the
> terminal. If gcc was complaining about hello.c missing then it would
> give you a more elaborate error message than what you have shown and if
> bash was complaining about gcc missing it would say "gcc: command not
> found".
And I would ask: "Is gcc on your path?" For example, on my system, which
has gcc installed, the response to "type gcc" is "/usr/bin/gcc". If I
do "type xxx" (some non-existent program) I get "xxx: not found".
Sounds to me like you may need to set up your PATH variable ...
If you're going to be using cygwin, then this should be a somewhat
familiar concept. One typical place to set it up is in your
.bash_profile file in your HOME directory (mine is /home/moss in
the cygwin tree).
Best _EM
next prev parent reply other threads:[~2020-07-06 16:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 12:57 Billie Healy
2020-07-06 16:41 ` ASSI
2020-07-06 16:59 ` Eliot Moss [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 9:07 pirracas77
2008-06-26 9:35 ` Dave Korn
2008-06-26 15:37 ` pirracas77
[not found] <f9dce6b30707120418yc2bea1axa699bea2d824e176@mail.gmail.com>
2007-07-12 12:38 ` Larry Hall (Cygwin)
2004-12-06 23:49 no " Kevin Smith
2002-12-13 16:03 No " ganglio
2000-03-27 6:01 Earnie Boyd
2000-03-27 7:56 ` Chris Faylor
2000-03-27 5:56 Earnie Boyd
2000-03-27 7:51 ` Chris Faylor
2000-03-26 16:11 Rick Rankin
2000-03-26 15:02 Rick Rankin
2000-03-26 15:09 ` Chris Faylor
2000-03-25 20:13 Rick Rankin
2000-03-26 9:13 ` Chris Faylor
2000-03-27 14:23 ` Michael Hirmke
2000-03-24 14:41 Eric Goforth
2000-03-25 13:07 ` Terry Lincoln
2000-03-25 19:44 ` Larry Hall (RFK Partners, Inc)
2000-03-25 19:50 ` Chris Faylor
2000-03-25 20:11 ` Larry Hall (RFK Partners, Inc)
2000-03-26 9:06 ` Chris Faylor
2000-03-27 7:25 ` Larry Hall (RFK Partners, Inc)
2000-01-15 4:50 Slate
2000-01-15 8:00 ` Heinz-Juergen Oertel
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=09da43ec-3235-dc9a-580a-916bc95616a9@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=Stromeko@nexgo.de \
--cc=cygwin@cygwin.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).