From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5672 invoked by alias); 30 Nov 2001 07:46:47 -0000 Mailing-List: contact sourcenav-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 5564 invoked from network); 30 Nov 2001 07:45:27 -0000 Message-Id: <200111300745.XAA23611@postman.bayarea.net> Subject: Re: Cygwin GNU tools v's GNUPro native tools Date: Tue, 13 Nov 2001 17:35:00 -0000 x-sender: jazzman@bayarea.net x-mailer: Claris Emailer 2.0v3, January 22, 1998 From: Syd Polk To: "Jordan" , Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2001-q4/txt/msg00027.txt.bz2 Jordan wrote: > >Hi all, > >What is meant by GNUPro (native) in the toolchain options of the build >setting window?? Does this mean that you cannot use the GNU tools >supplied in the Cygwin distribution with SN but instead need to >purchase the GNUPro toolkit native for windows? > >I can understand this from a marketing exercise but logically how can >this be? If SN goes looking for gcc via the PATH variable in windows >the same way it does under Linux, why would it not be satisfied with >C:\cygwin\bin\gcc? > >Confused as ever? > >J. There is no difference. The only thing is that some versions of gdb don't support the command line option that SN needs to run (--external-editor), whereas the GnuPro version does.