From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29641 invoked by alias); 21 Jul 2005 03:05:48 -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 29588 invoked by uid 22791); 21 Jul 2005 03:05:41 -0000 Received: from c-24-61-23-223.hsd1.ma.comcast.net (HELO cgf.cx) (24.61.23.223) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 21 Jul 2005 03:05:41 +0000 Received: by cgf.cx (Postfix, from userid 201) id 4AA6C13C0EC; Wed, 20 Jul 2005 23:05:38 -0400 (EDT) Date: Thu, 21 Jul 2005 03:05:00 -0000 From: Christopher Faylor To: gcc@gcc.gnu.org, DJ Delorie , fxcoudert@gmail.com, dannysmith@users.sourceforge.net, gcc-patches@gcc.gnu.org, ian@airs.com Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32 Message-ID: <20050721030538.GH23290@trixie.casa.cgf.cx> Mail-Followup-To: gcc@gcc.gnu.org, DJ Delorie , fxcoudert@gmail.com, dannysmith@users.sourceforge.net, gcc-patches@gcc.gnu.org, ian@airs.com References: <42DCC2D5.5010900@gmail.com> <20050719195238.GB23513@trixie.casa.cgf.cx> <42DD5C82.4040502@gmail.com> <20050719201404.GA26817@trixie.casa.cgf.cx> <20050719202104.GA14525@nevyn.them.org> <20050721021003.GA23290@trixie.casa.cgf.cx> <200507210225.j6L2P6YI000508@greed.delorie.com> <20050721024039.GF23290@trixie.casa.cgf.cx> <200507210258.j6L2w5Qv000903@greed.delorie.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507210258.j6L2w5Qv000903@greed.delorie.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-07/txt/msg00885.txt.bz2 On Wed, Jul 20, 2005 at 10:58:05PM -0400, DJ Delorie wrote: >> Is that actually true, though? Doesn't GNU ld try to locate files >> relative to its invoked path? > >Sometimes, for sysroots and ldscripts. I wouldn't expect MinGW (or >any native linker) to use this feature. GCC usually passes ld >whatever path specifications it needs. Wouldn't that mean that 'cp' is a valid fallback even for non-GNU lds? >> Since we know that mingw uses GNU ld couldn't we prewire this action >> into configure by default and avoid the need for this kind of >> system-specific behavior in the makefile? > >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? >That gives us the functionality of symlinks even on platforms like >MinGW that support neither symlinks nor shell scripts, without the >nasty side effects of using cp or symlinks. > >Heck, it can even search $PATH for us. That sounds like a good idea to me. cgf