Mail Archives: cygwin/2003/02/02/14:07:24
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/
- Raw text -