X-Spam-Check-By: sourceware.org
From: Daniel Villeneuve <dvilleneuve AT kronos DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Message-ID: <18124.41239.477455.371956@hilo.ca.kronos.com>
Date: Wed, 22 Aug 2007 16:48:23 -0400
To: cygwin AT cygwin DOT com
Subject: cross-compilation linux->cygwin and gcc-3.4.4
X-Mailer: VM 7.17 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
Reply-To: dvilleneuve AT kronos DOT com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l7MKmZil002125

Hi,

I'm in the process of updating my cross-compilation
environment from cygwin-1.5.12 to cygwin-1.5.24, mainly
because we have had code generation problems with
gcc-3.3.3-3 from the former.

However, I get the following message

    No support for this host/target combination

from gcc-3.4.4/libstdc++-v3/configure (crossconfig.m4), because
indeed cygwin is not mentioned in any of the clauses of the main
case statement.

Looking at what is done for mingw32 (only some checks), would it be
safe to hand-edit this configure script to skip the "exit 1"
associated with the message and let the compilation continue?

Is there something else I am missing in my distro (of course, I've
patched the sources using the distributed file).

Thanks for any help,

Daniel Villeneuve
Kronos


--
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/