From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20697 invoked by alias); 11 May 2005 23:13:22 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20319 invoked from network); 11 May 2005 23:13:13 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 11 May 2005 23:13:13 -0000 Received: from zaretski (IGLD-83-130-254-105.inter.net.il [83.130.254.105]) by legolas.inter.net.il (MOS 3.5.6-GR) with ESMTP id EIV04136 (AUTH halo1); Thu, 12 May 2005 02:13:07 +0300 (IDT) Date: Wed, 11 May 2005 23:16:00 -0000 From: "Eli Zaretskii" To: gdb-patches@sources.redhat.com Message-ID: <01c5567e$Blat.v2.4$b211b4a0@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 In-reply-to: <20050511191550.GB18308@trixie.casa.cgf.cx> (message from Christopher Faylor on Wed, 11 May 2005 15:15:50 -0400) Subject: Re: MinGW build instructions Reply-to: Eli Zaretskii References: <01c55598$Blat.v2.4$baecd3c0@zahav.net.il> <428113E4.9090807@codesourcery.com> <01c5559e$Blat.v2.4$1b76ee60@zahav.net.il> <20050510203127.GA10559@nevyn.them.org> <20050510213821.GA8600@trixie.casa.cgf.cx> <20050510214218.GA8776@trixie.casa.cgf.cx> <01c555f9$Blat.v2.4$330af160@zahav.net.il> <4281B26C.60208@codesourcery.com> <20050511161153.GH10119@trixie.casa.cgf.cx> <01c55659$Blat.v2.4$34414ce0@zahav.net.il> <20050511191550.GB18308@trixie.casa.cgf.cx> X-SW-Source: 2005-05/txt/msg00257.txt.bz2 > Date: Wed, 11 May 2005 15:15:50 -0400 > From: Christopher Faylor > > >Also, the configuration that you suggest: some part of Cygwin and the > >MinGW compiler, will probably suffer from incompatibilities due to > >Cygwin file names that the MinGW compiler probably doesn't understand, > >symlinks that the utilities such as ln support, but the MinGW compiler > >might not, etc. > > I don't see why. Because the configure script runs the compiler to probe the system. If configure creates symlinks, the compiler might fail because it doesn't support them. Also, in some packages, the script creates symlinks which the compiler then needs to access during the build, like in the case of nm-* files in GDB. > It's odd that you apparently don't like my not being specific enough but > then go on to postulate general problems with things that you haven't > tried. I didn't postulate them, I just suggested that perhaps there might be a problem. FWIW, in my few attempts to build GNU packages with MinGW I found that a Unixy shell is the only missing part, as long as you don't need to run Automake, Autoconf, etc. After some looking around, I used the MinGW ports of the standard utilities and a Windows port of zsh that I found on the net. It worked quite well, but that was a simple package, nowhere near the complexities of GDB, with its multilevel subdirectories. > >So I don't really understand why you don't like their alternative. Is > >it known to have some serious problems? > > How much would you like someone saying "I've got this new version of > tools that I've called CFGPP" if the tools were a repackaging of DJGPP > with some patches? Ah, okay. I thought there were some technical problems. Thanks for the info.