Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 2 Feb 2003 14:07:54 -0500
From: Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin Compile of NetBSD 1.6
Message-ID: <20030202190754.GB8930@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3E3C040C DOT 7000204 AT sonic DOT net> <3E3D6371 DOT 9090901 AT sonic DOT net> <001101c2caec$b81dab80$c2e686d9 AT webdev> <004401c2caed$c0da3120$78d96f83 AT pomello>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004401c2caed$c0da3120$78d96f83@pomello>
User-Agent: Mutt/1.5.1i

On Sun, Feb 02, 2003 at 07:03:20PM -0000, Max Bowsher wrote:
>Elfyn McBratney wrote:
>>>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
>
>Or find out why it is finding a cc at all, and stop it.  Run "which cc"
>to find out where the cc is, if it is in your PATH.  If that doesn't
>find anything, then hack build.sh to preserve config.log, and check
>that.

Or, even, just give up since the likelihood of actually being able to
build NetBSD under Cygwin with little or no knowledge of cross compilers
or symlinks or log files is remote at best.

This is not going to be a "fix a few problems and it works" type of
exercise.

cgf

--
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/