Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <001101c2caec$b81dab80$c2e686d9@webdev> From: "Elfyn McBratney" To: "cygwin" , "Christos Dritsas" References: <3E3C040C DOT 7000204 AT sonic DOT net> <3E3D6371 DOT 9090901 AT sonic DOT net> Subject: Re: Cygwin Compile of NetBSD 1.6 Date: Sun, 2 Feb 2003 18:55:16 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > So, what appears to be happening is that the build.sh script is > recoginizing "cc" when checking for "gcc". Cygwin does not appear to > recognize "cc" as a compiler on it - attempted test compiles with the > "cc" comand. Without changing anything in the build scripts, is there an > easy way to tell the Cygwin bash enviornment to recognize "cc" as "gcc"? > I did attempt to use a name-value pair in the bash enviornment (as per > the bash man page - "CC=C:\cygwin\bin\gcc.exe"), but it did not work for > me. You can create a symbolic link from gcc to cc: $ cd /bin && ln -s gcc cc Regards, Elfyn McBratney elfyn AT exposure DOT org DOT uk www.exposure.org.uk -- 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/