From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26757 invoked by alias); 21 Jul 2005 06:20:59 -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 26707 invoked by uid 22791); 21 Jul 2005 06:20:54 -0000 Received: from perpugilliam.csclub.uwaterloo.ca (HELO perpugilliam.csclub.uwaterloo.ca) (129.97.134.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 21 Jul 2005 06:20:54 +0000 Received: by perpugilliam.csclub.uwaterloo.ca (Postfix, from userid 20006) id 4428FA85D4; Thu, 21 Jul 2005 02:20:53 -0400 (EDT) Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32 To: gcc@gcc.gnu.org Date: Thu, 21 Jul 2005 06:20:00 -0000 MIME-Version: 1.0 Message-Id: <20050721062053.4428FA85D4@perpugilliam.csclub.uwaterloo.ca> From: rridge@csclub.uwaterloo.ca (Ross Ridge) X-SW-Source: 2005-07/txt/msg00889.txt.bz2 >A thought occurs to me... we *know* how to build build-system >executables, like gen*.exe. Why can't we have small C programs that >know where as/ld are, know how to exec them portably (libiberty), etc? You already have a not-so-small C program that's supposed to know where as and ld are. Unfortunately, it seems to get this wrong is some case or another and thus these rules for "linking" the utilities into the build directory were added. Maybe it's the gcc front end that needed to be fixed, not the makefile. Ross Ridge -- l/ // Ross Ridge -- The Great HTMU [oo][oo] rridge@csclub.uwaterloo.ca -()-/()/ http://www.csclub.uwaterloo.ca/u/rridge/ db //