From owner-freebsd-current@FreeBSD.ORG Fri May 2 05:24:11 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D59EF79A; Fri, 2 May 2014 05:24:11 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E21A19B5; Fri, 2 May 2014 05:24:11 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-232-70.lns20.per1.internode.on.net [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s425Nwag084204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 1 May 2014 22:24:00 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <53632BE8.9070000@freebsd.org> Date: Fri, 02 May 2014 13:23:52 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Brooks Davis , Warner Losh Subject: Re: POLA.. missing --sysroot option in ld? References: <536061A9.7030502@freebsd.org> <53607ABD.1000605@freebsd.org> <20140501131830.GA9578@lor.one-eyed-alien.net> In-Reply-To: <20140501131830.GA9578@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2014 05:24:11 -0000 On 5/1/14, 9:18 PM, Brooks Davis wrote: > On Wed, Apr 30, 2014 at 11:02:31PM -0600, Warner Losh wrote: >> On Apr 29, 2014, at 10:23 PM, Julian Elischer wrote: >> >>> On 4/30/14, 10:36 AM, Julian Elischer wrote: >>>> In our 8.0 based systems at $JOB our build environment made heavy use of the --sysroot option in gcc and ld. >>>> >>>> We are trying to move up to a newer release but suddenly the --sysroot option has disappeared. >>>> >>>> we get the message "/usr/bin/ld: this linker was not configured to use sysroots" >>> more spefically the following command (from 'configure') fails on "near 9" >>> and succeeds on 8.0. >>> >>> configure:3352: /usr/bin/gcc -Wall -Wno-unused-parameter -nostdinc -isystem /usr/build/buildroot/tools/x86_gcc4.2.4/usr/include --sysroot /usr/build/buildroot/tools/x86_gcc4.2.4 -Wall -Wno-unused-parame >>> ter -nostdinc -isystem /usr/build/buildroot/tools/x86_gcc4.2.4/usr/include --sysroot /usr/build/buildroot/tools/x86_gcc4.2.4 --sysroot /usr/build/buildroot/tools/x86_gcc4.2.4 -L/usr/build/buildroot/too >>> ls/x86_gcc4.2.4/lib -L/usr/build/buildroot/tools/x86_gcc4.2.4/usr/lib conftest.c >&5 >>>> Does anyone know what happened? and when, and by who? >>>> I have looked in the Makefiles and configuration files in SVN and I can't see a change that would have done this.. >>>> of course the building of these tools is rather complex so I may have missed some place.. >> Yea, I looked too and don?t see anything. I thought it was broken in more like 2005 not 2011. You?re only hope is to bisect the tree down to the change that caused it? > It's been broken since at least the last binutils import and probably > longer since the inane ld behavior of activating --sysroot only when > built with a specified sysroot is from upstream. The fix is trivial, just > merge r257268 and r257530 to the branch you are using. yeah I did that yesterday.. worked like a charm. > -- Brooks