Problems building RTEMS for M68k in CYGWIN environment

[Joel Sherrill]

> checking for i686-pc-cygwin-gcc.... no
>checking for gcc... gcc
>checking for C compile default output file name... configure: error: C


I am pretty sure this indicates the native compiler is not working.  Can 
you
actually compile and run a native "hello world"?

--joel

Sreejith kurup wrote:

>Try making the folder \tmp\rtemsdocs-4.6.5 in the folder b-gcc or the folder
>containing b-gcc.
>
>regards
>sreejith
>
>-----Original Message-----
>From: Chris Welch [mailto:cwelch at neumes.com]
>Sent: Saturday, April 22, 2006 10:51 PM
>To: rtems-users at rtems.com
>Subject: RE: Problems building RTEMS for M68k in CYGWIN environment
>
>
>Watch out for definitions for the Microchip tools as well.  I got badly
>burned with very strange make errors that took a couple of days to isolate
>to the definitions set up for Microchip tools.
>
>I believe you'll find them if you search for anything with MCC in your
>environment variables.
>
>----
>Chris Welch, Neumes Consulting, PC and UNIX Solutions
>mailto:cwelch at neumes.com (613)797-7831 FAX:(613)838-5602
>http://www.neumes.com
>
>-----Original Message-----
>From: Joel Sherrill [mailto:joel.sherrill at oarcorp.com]
>Sent: Friday, April 21, 2006 11:17 AM
>To: Swain, Mark T
>Cc: rtems-users at rtems.com
>Subject: Re: Problems building RTEMS for M68k in CYGWIN environment
>
>Cygwin sometimes inherits environment variables from Windows that are
>specific
>to Visual Studio and confuse GCC.  Do a "env" command and look for variables
>like CC, LIBS, etc that are set.
>
>But you need to also make sure you can compile and run a native hello world.
>That's what appears to have failed.  Look in config.log for details.
>
>--joel
>
>Swain, Mark T wrote:
>
>  
>
>>Hello all,
>>
>>Please forgive the ignorant questions but I'm a "newbie" to RTEMS and
>>    
>>
>trying to get past the learning curve. At this point I'm just trying to
>install rtems 4.6.5 for a m68k target (actually its a M68377, CPU32 based)
>and a gen68340 BSP. The host I'm using is a Windows XP machine running
>CYGWIN.
>  
>
>>I've been following the instructions as detailed in the "Getting Started
>>    
>>
>with RTEMS" documentation and all has went as planned until now. I'm having
>problems with the actual building of RTEMS (Chapter 5). Specifically the
>problem appears to be when I attempt to configure the environment. The
>configure command I'm executing looks like the following:
>  
>
>>../rtems-4.6.5/configure --target=m68k-rtems --enable-rtembsp=gen68340
>>
>>That resulted in the checking of several prereqs but fails at the gcc check
>>    
>>
>with the following error:
>  
>
>>checking for i686-pc-cygwin-gcc.... no
>>checking for gcc... gcc
>>checking for C compile default output file name... configure: error: C
>>    
>>
>compiler cannot create executables
>  
>
>>See 'config.log' for more details
>>configure: error: /bin/sh '../../../rtems-4.6.5/tools/build/configure'
>>    
>>
>failed for tools/build
>  
>
>>I can't find any relavant info in the config.log file. I don't understand
>>    
>>
>the error. Is RTEMS looking for gcc and can't find it? I checked the path
>and it appears to point to the correct locations. Any ideas???
>  
>
>>Mark
>>
>>
>>
>>***************************************************************************
>>    
>>
>*************
>  
>
>>Note:  If the reader of this message is not the intended recipient, or an
>>    
>>
>employee or agent responsible for delivering this message to the intended
>recipient, you are hereby notified that any dissemination, distribution or
>copying of this communication is strictly prohibited. If you have received
>this communication in error, please notify us immediately by replying to the
>message and deleting it from your computer. Thank you.
>  
>
>>***************************************************************************
>>    
>>
>*************
>  
>
>>    
>>
>
>
>
>
>
>http://www.patni.com
>World-Wide Partnerships. World-Class Solutions.
>_____________________________________________________________________
>
>This e-mail message may contain proprietary, confidential or legally
>privileged information for the sole use of the person or entity to
>whom this message was originally addressed. Any review, e-transmission
>dissemination or other use of or taking of any action in reliance upon
>this information by persons or entities other than the intended
>recipient is prohibited. If you have received this e-mail in error
>kindly delete  this e-mail from your records. If it appears that this
>mail has been forwarded to you without proper authority, please notify
>us immediately at netadmin at patni.com and delete this mail. 
>_____________________________________________________________________
>  
>