From owner-freebsd-ports@FreeBSD.ORG Thu Aug 10 17:46:03 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59F4116A4DD for ; Thu, 10 Aug 2006 17:46:03 +0000 (UTC) (envelope-from ssedov@mbsd.msk.ru) Received: from com1.ht-systems.ru (com1.ht-systems.ru [83.97.104.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD4D243D81 for ; Thu, 10 Aug 2006 17:46:00 +0000 (GMT) (envelope-from ssedov@mbsd.msk.ru) Received: from [217.118.83.1] (helo=fonon.realnet) by com1.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1GBEbR-0005PZ-RK for freebsd-ports@freebsd.org; Thu, 10 Aug 2006 21:45:56 +0400 Received: from localhost (localhost [127.0.0.1]) by fonon.realnet (Postfix) with ESMTP id 5B80A1261B for ; Thu, 10 Aug 2006 21:45:16 +0600 (YEKST) Date: Thu, 10 Aug 2006 21:45:16 +0600 From: Stanislav Sedov To: freebsd-ports@freebsd.org Message-ID: <20060810214516.7e0ff056@localhost> In-Reply-To: <44DB5692.6040005@gmx.de> References: <44DB5692.6040005@gmx.de> Organization: MBSD labs, Inc. X-Operating-System: FreeBSD X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_X379ay6uY92/fOn/lo9=7__"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona 1.6.0 Subject: Re: ports without configure do not receive CC 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: Thu, 10 Aug 2006 17:46:03 -0000 --Sig_X379ay6uY92/fOn/lo9=7__ Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On Thu, 10 Aug 2006 17:53:54 +0200 "[LoN]Kamikaze" mentioned: > Ports that do not set CC in their configure target don't get informed abo= ut the value of CC because it is only appended to MAKE_ENV for the configur= e target. I think it doesn't present a big problem for i don't know a single port that sets up value of CC variable in it's Makefile. Thus, we have only 3 scenarios: 1) CC is set up on make commandline (e.g. make CC=3Dxxx). In that case make program will export value of CC to enviropment and every make program executed will receive it 2) CC is exported to sheel enviropment. This case is obvious. 3) CC was defined in make.conf. In that case if GNU make isn't used in do-build stage make will re-read make.conf and, thus, honor CC's value. I think we should not consider GNU make's case - it's used much less often, than our original make program. --=20 Stanislav Sedov MBSD labs, Inc. =F2=CF=D3=D3=C9=D1, =ED=CF=D3=CB=D7=C1 http://mbsd.msk.ru -------------------------------------------------------------------- If the facts don't fit the theory, change the facts. -- A. Einstein -------------------------------------------------------------------- PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 --Sig_X379ay6uY92/fOn/lo9=7__ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFE21SMK/VZk+smlYERAgpAAJwKl/e9jC5YMF/bQlrV1XDtwH48LwCghEbf yNoVOOjDBykpxUESZOsoLXA= =Ma4f -----END PGP SIGNATURE----- --Sig_X379ay6uY92/fOn/lo9=7__--