From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29465 invoked by alias); 27 Jan 2004 18:38:14 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 29448 invoked from network); 27 Jan 2004 18:38:13 -0000 Received: from unknown (HELO mail01.pge.com) (131.89.128.13) by sources.redhat.com with SMTP; 27 Jan 2004 18:38:13 -0000 Received: from mail04.comp.pge.com (mail04dmz [10.252.0.60]) by mail01.pge.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i0RIcAr11853; Tue, 27 Jan 2004 10:38:10 -0800 (PST) Received: from mdssdev05.comp.pge.com (mdssdev05.comp.pge.com [10.244.96.61]) by mail04.comp.pge.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i0RIc8Q01075; Tue, 27 Jan 2004 10:38:08 -0800 (PST) Received: (from esp5@localhost) by mdssdev05.comp.pge.com (8.9.1b+Sun/8.9.1) id KAA11161; Tue, 27 Jan 2004 10:35:27 -0800 (PST) X-Authentication-Warning: mdssdev05.comp.pge.com: esp5 set sender to esp5@pge.com using -f Date: Tue, 27 Jan 2004 18:38:00 -0000 From: "Edward S. Peschko" To: Marcel Cox Cc: gcc@gcc.gnu.org Subject: Re: open watcom compiling gcc on win32 Message-ID: <20040127183526.GA11059@mdssdev05.comp.pge.com> References: <20040127073509.GB10278@mdssdev05.comp.pge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2004-01/txt/msg02023.txt.bz2 On Tue, Jan 27, 2004 at 08:00:51AM +0000, Marcel Cox wrote: > Edward S. Peschko wrote: > > > I was wondering if open-watcom could be used to compile gcc on > > win32... I was hoping to do so under cygwin.. > > > > If so, what are the steps for doing so? If not, what's the preferred > > compiler for building gcc on win32? > > You should take a look at the Mingw32 project which is a native GCC > port to win32 platforms: > > http://www.mingw.org/ > well, that's the point - I need a compiler that can link with VC++ dlls *and* compile the gnu toolchain. Right now, both python and perl are split into two 'personalities' : you can either compile modules *for* win32 or modules *for* unix, but you can't do both and hope to have them play well together. Plus, certain third-party APIs don't work well with mingw - well, pretty much all third-party APIs don't work well because they are all compiled for Borland or VC++. And COM just plain sucks - most tool people assume that you have VC++ or Borland. So, as far as I see it, watcom is the only viable choice for what I want to do. And if I could compile gcc with watcom, I could pretty much compile anything gnu-like. Ed