From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18529 invoked by alias); 11 May 2005 16:12:02 -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 18484 invoked from network); 11 May 2005 16:11:53 -0000 Received: from unknown (HELO cgf.cx) (66.30.17.189) by sourceware.org with SMTP; 11 May 2005 16:11:53 -0000 Received: by cgf.cx (Postfix, from userid 201) id BDE9213C9F2; Wed, 11 May 2005 12:11:53 -0400 (EDT) Date: Wed, 11 May 2005 18:45:00 -0000 From: Christopher Faylor To: Mark Mitchell , gdb-patches@sources.redhat.com, Eli Zaretskii Subject: Re: MinGW build instructions Message-ID: <20050511161153.GH10119@trixie.casa.cgf.cx> Mail-Followup-To: Mark Mitchell , gdb-patches@sources.redhat.com, 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4281B26C.60208@codesourcery.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00247.txt.bz2 On Wed, May 11, 2005 at 12:21:16AM -0700, Mark Mitchell wrote: >Eli Zaretskii wrote: >>As an aside, what little experience I have in porting Unix programs to >>MinGW tells me that setting up an environment to build a package is >>not a trivial job. There are issues with what shell to use and how to >>set it up, what ports of auxiliary tools (Coreutils, Grep, Awk, etc.) >>to use and how to set them up, what non-default libraries to install >>and link against (the MinGW libraries such as libiberty, Libgw32c), etc. >> >>So perhaps, if we are going to have an alive MinGW port, it is a good >>idea to have a README.MinGW file in the distro that would describe how >>to build such a port of GDB. A description of the setup Mark uses to >>work on the port would be a good starting point. > >I'd be happy to write it up -- but what I do is simple: I cheat. I use >cross compilers from i686-pc-linux-gnu to i686-ming32. If it would be >useful for me to show how I configure and build GDB like that, I'm happy >to write that up; just let me know. Some people use the cygwin-fork (grr...) MSYS to do mingw development. It should contain every package that you need to build gdb, I think. And, I am mentioning this through gritted teeth in the interests of full disclosure. At least one of the mingw developers just uses cygwin to do mingw development, which, of course, seems to be to be the ultimate solution if you want to work on windows. AFAIK, cygwin's libraries like autoconf and gettext seem to be updated more frequently than MSYS. 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... cgf