From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19796 invoked by alias); 10 Dec 2001 20:34:30 -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 19674 invoked from network); 10 Dec 2001 20:33:12 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 10 Dec 2001 20:33:12 -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 MAA25976; Mon, 10 Dec 2001 12:33:09 -0800 (PST) Received: (from dj@localhost) by greed.delorie.com (8.11.6/8.11.6) id fBAKUEU24547; Mon, 10 Dec 2001 15:30:14 -0500 Date: Mon, 10 Dec 2001 12:36:00 -0000 Message-Id: <200112102030.fBAKUEU24547@greed.delorie.com> From: DJ Delorie To: jsturm@one-point.com CC: gcc@gcc.gnu.org In-reply-to: (message from Jeff Sturm on Sun, 9 Dec 2001 11:02:12 -0500 (EST)) Subject: Re: mingw32 target broken [cygwin as well] [the saga continues] References: X-SW-Source: 2001-12/txt/msg00535.txt.bz2 > This never seemed like desirable behavior to me, in part because newlib > isn't even GNU software. I'd prefer that configure attempt to link a > program before it assumes it cannot. Newlib is an operating system, just like solaris or IRIX. It doesn't have to be GNU software for us to support it, it just has to support and allow GNU software. And you can't always do a test link with cross compilers, because you may not have built enough support stuff (crt0, libc, gas/ld) to do so. In fact, for a canadian cross, you can't link *at all* because you just can't run the linker. Newlib is a popular target for GNU tools, so people have contributed extra support for it. There are other platforms we do this for, like cygwin and vxworks. > > I've also noticed that the configure in the root directory of the gcc > > checkout does not pass the --target=$TARGET option to the invocation > > of configure for libstdc++-v3, although it does pass --with-target-dir > > In the target subdirs, "target" becomes "host". Yeah, that confuses people, but it does make sense. "host" is what you're building *for*. For target libraries, you're building for the --target, so $host is --target. $build is what you're building *on*. $host is what you're building *for*. $target is what the stuff you're building produces code for. With these definitions, it's meaningless to use $target with a library, because libraries do not themselves produce code.