From owner-freebsd-current@FreeBSD.ORG Wed Apr 30 02:36:34 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0D3D700 for ; Wed, 30 Apr 2014 02:36:34 +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 9AD95184C for ; Wed, 30 Apr 2014 02:36:34 +0000 (UTC) Received: from Julian-MBP3.local (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 s3U2aUZD075085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 29 Apr 2014 19:36:32 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <536061A9.7030502@freebsd.org> Date: Wed, 30 Apr 2014 10:36:25 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: FreeBSD Current Subject: POLA.. missing --sysroot option in ld? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 30 Apr 2014 02:36:34 -0000 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" 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.. julian