Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: Fred Fish <fnf AT ninemoons DOT com>
Reply-To: fnf AT ninemoons DOT com
To: cygwin AT cygwin DOT com
Subject: Building Linux hosted cross compiler to cygwin target
Date: Tue, 13 Jan 2004 08:04:54 -0700
User-Agent: KMail/1.5.4
Cc: fnf AT ninemoons DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200401130804.55078.fnf@ninemoons.com>

Does anyone have a pointer to a detailed set of instructions for
building a linux hosted (i686-pc-linux-gnu) toolchain to a cygwin
target (i686-pc-cygwin) starting from the bare CVS sources with no
precompiled/preinstalled components?

I've spent a couple of days trying to build this from the current CVS
sources for binutils, gcc, and winsup, with a moderate amount of
success but now am getting bogged down in what appears to be some
messy interdepencies between the cygwin and mingw32 targets.

Is there a more appropriate mailing list for this question?

Thanks!

-Fred



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/