From owner-freebsd-ports@FreeBSD.ORG Tue Jun 22 15:27:00 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32401106564A for ; Tue, 22 Jun 2010 15:26:59 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:470:8940:10::1]) by mx1.freebsd.org (Postfix) with ESMTP id 86A5B8FC1A for ; Tue, 22 Jun 2010 15:26:59 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:470:8940:10::1]) by tiktik.epipe.com (8.14.3/8.14.3) with ESMTP id o5MFQwPn067712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jun 2010 15:26:58 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com o5MFQwPn067712 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1277220418; x=1277825218; bh=2Ug2ccsSJsm9KfbIXlO5t4A4NuVTi1003N/Wd1CDMtA=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=pUMKryYxIg0ZPgWz4bfvzz6UfiFcVMH3gAZY5QLc/VyZr45NoJKQ1GcTPel4pCm9Y Iv+IdMEj2eRBDevPJBprHSWeIDAXCQUsrs2bxssBDVD1yh9cT9vZLG7Yp5pjx9Xxtk jiAkpOr6OnCVrhIkFitrKC0FUVxtav2B3FbxLIs8= Date: Tue, 22 Jun 2010 15:26:53 +0000 (UTC) From: Janne Snabb To: bf1783@gmail.com In-Reply-To: Message-ID: References: <4C206505.2060601@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.5 (tiktik.epipe.com [IPv6:2001:470:8940:10::1]); Tue, 22 Jun 2010 15:26:58 +0000 (UTC) Cc: freebsd-ports@freebsd.org Subject: Re: mail/thunderbird3 does not build with gcc 4.5.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 15:27:00 -0000 On Tue, 22 Jun 2010, b. f. wrote: > I can tell you right now from my own experiences that the ports > infrastructure and many individual ports do not respect the necessary > compiler and toolchain-related variables. Part of this problem is that the Porters Handbook only tells porters to respect CC, CXX and CFLAGS, nothing else. This issue came up as well in the "Building ports with stack-protector" thread a couple of weeks ago (by yourself). What would be the comprehensive list of variables to respect? There are already quite many from the top of my head: CC CFLAGS CXX CXXFLAGS CPP CPPFLAGS LD LDFLAGS AS AFLAGS AR ARFLAGS RANLIB INSTALL OBJCOPY Some of the above would generally be required to be respected only when cross-compiling to an another architecture. I have been thinking of making a test build of all ports with some useless options in relevant variables and capturing output or doing ktrace to figure out which ports respect those flags and which do not. Haven't gotten around to actually doing it just yet :). Another work-around would be to make a directory containing wrapper-shell-scripts with the names like cc, gcc, ld, cpp etc. and make them invoke the desired tools with desired flags. That directory would be placed in the beginning of PATH before compiling ports. This would be a quicker alternative to patching lots of ports. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/