From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2485 invoked by alias); 10 Dec 2001 20:52:29 -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 767 invoked from network); 10 Dec 2001 20:51:11 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 10 Dec 2001 20:51:11 -0000 Received: from greed.delorie.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id MAA28006; Mon, 10 Dec 2001 12:51:07 -0800 (PST) Received: (from dj@localhost) by greed.delorie.com (8.11.6/8.11.6) id fBAKmCM24745; Mon, 10 Dec 2001 15:48:12 -0500 Date: Mon, 10 Dec 2001 12:57:00 -0000 Message-Id: <200112102048.fBAKmCM24745@greed.delorie.com> From: DJ Delorie To: jsm28@cam.ac.uk CC: jsturm@one-point.com, gcc@gcc.gnu.org In-reply-to: (jsm28@cam.ac.uk) Subject: Re: mingw32 target broken [cygwin as well] [the saga continues] References: X-SW-Source: 2001-12/txt/msg00541.txt.bz2 > But for a Canadian cross, surely you should have a full build x target > toolchain - including the linker and target libraries - installed (as well > as a build x host one) before building the Canadian cross? (At least, > etc/configure.texi in src says so.) There's no guarantee it's the same version as the library you're building though. But you're right, we should have a working linker. It's *executing* the tests that you can't rely on. And for Cygwin it's even worse, as parts of libiberty.a are used to build cygwin1.dll, so if you did the linking test you wouldn't build the very functions cygwin pulls from libiberty to build the dll!