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: <20020707040221.3064.qmail@web40208.mail.yahoo.com> Date: Sat, 6 Jul 2002 21:02:21 -0700 (PDT) From: Motivus Subject: Re: Compiling with Borland's bcc32... more simply stated To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii > 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. > > cgf 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. Thanks for the help! I mean it!!! Mvus __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.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/