X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=kq7ESpXT3rWwqRSR8YO2b/2IxEJZXDSyvPoyVGjvHHV il/6wtLul8K4OKUPPcw6Hg/ldpa8CiZhLRnHddtW+dt8WybpYmYQfF7lQPCcVcDV sBUHj1dHwdBYZPEqefP7JxixBHEqVfw6HMDh24nIL1xvDNgWaibCCnnniPGgK9HA = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=2YYo6QEiBAbB23PmKw23mhwZLlA=; b=JqwOX1mCz42Nljtp2 NVVTwgG4CRZ4IWgqE9tVswtim1H6JsDTR2SLtH8Ouc85cq0+pX5ZC1fgOVoeXkHU 3iVVHvdO4jXL2HqQUuY4hchP3xhB0hIkPFzXa0zqNSI0dj2ijQfTGKzDCH24o+TS lUP9EwK0GxoVKBdqDy3/CxaNwU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: Ishtar.tlinx.org Message-ID: <52D6FD6F.9000907@tlinx.org> Date: Wed, 15 Jan 2014 13:28:15 -0800 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problem w/ gcc: sensitive to path it was invoked on... References: <52D639E5 DOT 9070304 AT tlinx DOT org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mark Geisert wrote: > Linda Walsh writes: > > Can't believe doesn't work for anyone. > > > > For me, I've tried multiple c progs (simple ones), > > You don't supply any example that shows your attempt and the resulting error > message(s). So maybe it (whatever *it* is) is working for everybody else? ---- Um...*simple*...like: law.Bliss> uname -a CYGWIN_NT-6.1 Athenae 1.7.27(0.271/5/3) 2013-12-09 11:54 x86_64 Cygwin law.Bliss> cd bin law.Bliss/bin> cat hello.c main() { printf("Hello World\n"); } law.Bliss/bin> gcc -o hello hello.c gcc: error: spawn: No such file or directory ==== > 1> Path: C:\Users\law.Bliss\bin\lib > 2> C:\usr\sbin > 3> C:\bin > 4> C:\sbin > 5> . > 6> C:\prog64\vim\gvim.exe > 7> C:\bin > 8> C:\sbin > ----- > > There was some discussion recently, last month I think, about the relative > position of /bin and /usr/bin in PATH mattering in a way it didn't use to. > I can't find the discussion or I'd link to it. But in any case you might > try substituting /usr/bin for /bin in your PATH setup. ---- ...hmmm...this is ugly... law.Bliss/bin> PATH=/usr/bin:$PATH law.Bliss/bin> gcc -o hello hello.c hello.c: In function 'main': hello.c:2:1: warning: incompatible implicit declaration of built-in function 'printf' [enabled by default] printf("Hello World\n"); ^ law.Bliss/bin> hello Hello World gcc is sensitive to the path it was invoked on?... gcc bug? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple