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 Date: Sun, 7 Jul 2002 00:06:07 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Compiling with Borland's bcc32... more simply stated Message-ID: <20020707040607.GA23012@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020707040221 DOT 3064 DOT qmail AT web40208 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020707040221.3064.qmail@web40208.mail.yahoo.com> User-Agent: Mutt/1.3.23.1i On Sat, Jul 06, 2002 at 09:02:21PM -0700, Motivus wrote: >>I suspect that the reason you didn't receive any replies is that your >>question doesn't make much sense. The whole point of cygwin is to >>provide an environment for building GNU tools without reliance of >>proprietary programs like those provided by Borland's. It is extremely >>unlikely that you'll be able to use Borland's compiler to build GNU >>tools for an ARM target. >> >>Just install gcc, like the rest of the Cygwin world, and use that. >>Rerun setup.exe (from Install Cygwin Now!), click on the plus sign next >>to "Devel" and then select gcc and any other tools you need. > >Oh. Now THAT'S embarrassing! I think I blinded myself by following a >procedure for building the GNU tools under UNIX and then configuring >them for cross-development on an ARM core. But I wasn't thinking >through the changes that would have to be made when coming at it from a >Cygwin environment. Theoretically, there should be no changes required for setting things up for cross development under the Cygwin environment. It should be roughly the same as under UNIX. >Thanks for the help! I mean it!!! De nada. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- 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/