From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailsrv.cs.umass.edu (mailsrv.cs.umass.edu [128.119.240.136]) by sourceware.org (Postfix) with ESMTPS id 6218E3857C77 for ; Mon, 6 Jul 2020 16:59:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6218E3857C77 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=moss@cs.umass.edu Received: from [192.168.0.36] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 0F057401E9CE; Mon, 6 Jul 2020 12:59:15 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: No such file or directory To: ASSI , cygwin@cygwin.com References: <87pn98ppeg.fsf@Otto.invalid> From: Eliot Moss Message-ID: <09da43ec-3235-dc9a-580a-916bc95616a9@cs.umass.edu> Date: Mon, 6 Jul 2020 12:59:13 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <87pn98ppeg.fsf@Otto.invalid> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2020 16:59:16 -0000 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