From owner-freebsd-current@FreeBSD.ORG Tue Apr 29 15:42:37 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 4CF57DBE; Tue, 29 Apr 2014 15:42:37 +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 1F97715A8; Tue, 29 Apr 2014 15:42:36 +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 s3TFgR74073515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 29 Apr 2014 08:42:30 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <535FC85E.9020002@freebsd.org> Date: Tue, 29 Apr 2014 23:42:22 +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: Ian Lepore Subject: Re: odd message from ld in -current around 9.0 branchpoint References: <535F3B87.4060706@freebsd.org> <1398773853.22079.2.camel@revolution.hippie.lan> In-Reply-To: <1398773853.22079.2.camel@revolution.hippie.lan> 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: Tue, 29 Apr 2014 15:42:37 -0000 On 4/29/14, 8:17 PM, Ian Lepore wrote: > On Tue, 2014-04-29 at 13:41 +0800, Julian Elischer wrote: >> I'm trying to compile a system based on current from just before the >> 9.x branchpoint. >> >> during hte build I got the following message: >> >> /usr/bin/ld: this linker was not configured to use sysroots >> >> does anyone have any idea what this means in a broader context? >> did I misconfigure something when I built this system? >> >> Julian >> > Are you using ccache? I vaguely remember some reports of this in the > past, and I think it was caused by using a version of ccache that wasn't > compatible with clang, or something along those lines. > > -- Ian > > > no I'm using gcc and (as far as I know) no ccache. This is compiling some 3rd party software.