From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26743 invoked by alias); 21 Jul 2005 03:00:34 -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 26699 invoked by uid 22791); 21 Jul 2005 03:00:21 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 21 Jul 2005 03:00:21 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1DvRID-0006eK-EX; Wed, 20 Jul 2005 23:00:13 -0400 Date: Thu, 21 Jul 2005 03:00:00 -0000 From: Daniel Jacobowitz To: DJ Delorie Cc: me@cgf.cx, gcc@gcc.gnu.org, dannysmith@users.sourceforge.net, fxcoudert@gmail.com, gcc-patches@gcc.gnu.org, ian@airs.com Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32 Message-ID: <20050721030013.GA25490@nevyn.them.org> Mail-Followup-To: DJ Delorie , me@cgf.cx, gcc@gcc.gnu.org, dannysmith@users.sourceforge.net, fxcoudert@gmail.com, 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/msg00884.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. I build mingw cross toolchains with sysroots :-) That'll be affected by this change. Of course, currently I cross-build them from --build=i686-linux, so it doesn't affect me directly. -- Daniel Jacobowitz CodeSourcery, LLC