From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28088 invoked by alias); 11 May 2005 18:45:07 -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 27470 invoked from network); 11 May 2005 18:44:46 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 11 May 2005 18:44:46 -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 EIU74294 (AUTH halo1); Wed, 11 May 2005 21:44:41 +0300 (IDT) Date: Wed, 11 May 2005 19:05:00 -0000 From: "Eli Zaretskii" To: gdb-patches@sources.redhat.com Message-ID: <01c55659$Blat.v2.4$34414ce0@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 In-reply-to: <20050511161153.GH10119@trixie.casa.cgf.cx> (message from Christopher Faylor on Wed, 11 May 2005 12:11:53 -0400) Subject: Re: MinGW build instructions Reply-to: Eli Zaretskii References: <01c55512$Blat.v2.4$85bf3480@zahav.net.il> <42804E09.9060508@codesourcery.com> <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> X-SW-Source: 2005-05/txt/msg00248.txt.bz2 > Date: Wed, 11 May 2005 12:11:53 -0400 > From: Christopher Faylor > > You don't have to install 700MB of cygwin to get things working. You > should be able to get away with just installing the bits that you need + > the mingw compiler. Or, it is possible that a i686-pc-mingw32-gcc > wrapper like: > > #!/bin/sh > exec gcc -mno-cygwin "$@" > > may "just work" with the cygwin version of gcc. The -mno-cygwin option > to gcc actually uses the mingw headers and libraries. Unfortunately, > there is a problem with cygwin-bleedover for libraries, though, so > you have to be careful not to specify any libraries on the command > line which exist on cygwin but not in mingw. This is something that > I keep meaning to fix in gcc/binutils... Thanks for the info. However, what is needed are precise instructions based on actual experience. If I were someone who needs for the first time compile a GNU package on Windows, it would not help me to know that such-and-such setup ``might just work''. The subtleties of running various ports of GNU tools on Windows are not something a newbie should need to learn as part of their first job. If someone knows exactly how to set up a build environment where the MinGW port of GDB can be built, please describe that. In particular, what parts of Cygwin need to be installed and how to run the compiler. 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 didn't try MSYS, but it sounds that they did resolve these problems in a more satisfactory manner. So I don't really understand why you don't like their alternative. Is it known to have some serious problems?