From owner-freebsd-toolchain@FreeBSD.ORG Mon Oct 15 15:27:56 2012 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8DAF8DE0; Mon, 15 Oct 2012 15:27:56 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id AFF208FC0A; Mon, 15 Oct 2012 15:27:55 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.5/8.14.5) with ESMTP id q9FFRtXR010836; Mon, 15 Oct 2012 10:27:55 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.5/8.14.5/Submit) id q9FFRt57010835; Mon, 15 Oct 2012 10:27:55 -0500 (CDT) (envelope-from brooks) Date: Mon, 15 Oct 2012 10:27:55 -0500 From: Brooks Davis To: Andriy Gapon Subject: Re: gcc46 --version incompatible with bsd.compiler.mk Message-ID: <20121015152755.GC10224@lor.one-eyed-alien.net> References: <5078102C.3070503@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ncSAzJYg3Aa9+CRW" Content-Disposition: inline In-Reply-To: <5078102C.3070503@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: toolchain@freebsd.org, Gerald Pfeifer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 15:27:56 -0000 --ncSAzJYg3Aa9+CRW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 12, 2012 at 03:42:20PM +0300, Andriy Gapon wrote: >=20 > Gerald, >=20 > $ gcc46 --version > gcc46 (FreeBSD Ports Collection) 4.6.3 >=20 > I think that the above should have just "gcc" instead of "gcc46". The ve= rsion is > reported separately from the compiler name. > The above output confuses bsd.compiler.mk. Alternatively I could alter bsd.compiler.mk to accept gcc[1-9][0-9] as gcc. You could also set COMPILER_TYPE to override the check entirely. The end state that got proposed at the Cambridge devsummit was that external toolchains would provide a makefile that bsd.compiler.mk could include that would handle this. An example implementation would be to add something like the following to the top of bsd.compiler.mk: =2Eif defined(TOOLCHAIN_MK) && exists(${TOOLCHAIN_MK}) =2Einclude ${TOOLCHAIN_MK} =2Eendif You could then point TOOLCHAIN_MK to a file that might look something like (I'm not sure the CC assignments would actually work here, but you get the idea): CC=3Dgcc46 CXX=3Dg++46 CPP=3Dcpp46 COMPILER_TYPE=3Dgcc COMPILER_FEATURES=3D -- Brooks --ncSAzJYg3Aa9+CRW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFQfCt6XY6L6fI4GtQRAgreAKDnGQhD1Mx0CpYOAS7PzNCMdwI5BACgiWn1 kG5N6wlovb+I57nyW+1YtOo= =KpdU -----END PGP SIGNATURE----- --ncSAzJYg3Aa9+CRW--