From owner-freebsd-questions@FreeBSD.ORG Thu Sep 25 01:01:03 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D844D1065691 for ; Thu, 25 Sep 2008 01:01:03 +0000 (UTC) (envelope-from fbsd06+2D=1a715566@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id A9C458FC13 for ; Thu, 25 Sep 2008 01:01:03 +0000 (UTC) (envelope-from fbsd06+2D=1a715566@mlists.homeunix.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in1.mxes.net (Postfix) with ESMTP id 52475164689 for ; Wed, 24 Sep 2008 20:45:25 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id D5E4ED05B3 for ; Wed, 24 Sep 2008 20:45:23 -0400 (EDT) Date: Thu, 25 Sep 2008 01:45:20 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080925014520.3850bb00@gumby.homeunix.com.> In-Reply-To: <200809250100.07383.fbsd.questions@rachie.is-a-geek.net> References: <48D7092B.1040503@brianwhalen.net> <200809241224.11455.fbsd.questions@rachie.is-a-geek.net> <48DA4E9C.8040905@brianwhalen.net> <200809250100.07383.fbsd.questions@rachie.is-a-geek.net> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: ccache on amd64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2008 01:01:03 -0000 On Thu, 25 Sep 2008 01:00:07 +0200 Mel wrote: > Since it fails on the link, I wonder if the wrong linker is called by > ccache. I'll see what I can find out when it quiets down, right now > machine is under heavy load. > > (It might just be the path you set in /etc/profile. I use only > the /etc/make.conf version, not set the path additionally and > make -f /usr/src/Makefile.inc1 -V LIB32WMAKE shows it's mangeling the > path) > world-cc does this: #!/bin/sh unset CCACHE_PATH export CCACHE_HASH_COMPILER exec /usr/local/libexec/ccache/cc "$@" So it unsets any ccache path variable set in /etc/profile. For the benefit of anyone that didn't follow the previous thread, the issue was that in building 32-bit libraries under amd64, extra arguments get passed to the compiler inside the CC variable definition, hence the problem with overriding CC/CXX. I doubt that those updated make.conf settings have had much testing, they were just something suggested in a thread. BTW I would suggest CCACHE_HASH_COMPILER is set globally, otherwise building world invalidates any cache object built with the default compiler. Only having it on for world is the default, but it seems perverse to me - I see most of the benefit of ccache on port building.