From owner-freebsd-ports@FreeBSD.ORG Wed Jul 10 07:32:49 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4B11BEF1 for ; Wed, 10 Jul 2013 07:32:49 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 0BEB61992 for ; Wed, 10 Jul 2013 07:32:48 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-ports@freebsd.org with esmtp (envelope-from ) id <1UwotF-000vZa-KQ>; Wed, 10 Jul 2013 09:32:41 +0200 Received: from e179076180.adsl.alicedsl.de ([85.179.76.180] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-ports@freebsd.org with esmtpsa (envelope-from ) id <1UwotF-003KNP-HV>; Wed, 10 Jul 2013 09:32:41 +0200 Date: Wed, 10 Jul 2013 09:32:36 +0200 From: "O. Hartmann" To: FreeBSD Ports Subject: CLANG 3.3/LLVM 3.3 question regarding devel/llvm vs. devel/llvm33 Message-ID: <20130710093236.4192847f@thor.walstatt.dyndns.org> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/yZ5Jjt0sr8dQ1LQlh6hM0xj"; protocol="application/pgp-signature" X-Originating-IP: 85.179.76.180 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 07:32:49 -0000 --Sig_/yZ5Jjt0sr8dQ1LQlh6hM0xj Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable No is 9.1-STABLE en route also equipted with CLANG 3.3, as it is with CURRENT. The ports system still differs between the "standard" devel/llvm, which is in fact LLVM 3.2 and devel/llvm33, which is then LLVM 3.3. devel/llvm installs some tools not in the standard manner, like llvm-config, which is then llvm-config33. This introduces some trouble and it seems a bit "out of sync". Is there a chance that devel/llvm becomes llvm 3.3 in a short time?=20 Regards, Oliver --Sig_/yZ5Jjt0sr8dQ1LQlh6hM0xj Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJR3Q4YAAoJEOgBcD7A/5N8dsgH/22cOjBZzp7/ugg0Rvl2Njb2 PLEeut0WkFOKD6c35ueHQPZsObFVnuvw99uuZufnVNU3HzgQS6h9vgoU5qXquR2T YytXIe14gqUUUfXw58TKq3zUGWgpiYgOwPwyonHE6jhGgbVVtjxvB63fHES3fD5E r8GPZu1m3RwcykrodGP+/L/ZPjBqYYdFOIAElBRZrTq0DnT4b0h8KK5eRsvdxsZK onIXdblpGelchHjwr0lsq12ScBh1DDgo1Yz9VjeKy4q2JRjrnXIroSLdNTCUKLbF /qYPv/NNZWp90esVz/QOpODqI4bdcu6dcgM5UYduonFuyyVQV5Zj1Gy1iue6Tp4= =RJqe -----END PGP SIGNATURE----- --Sig_/yZ5Jjt0sr8dQ1LQlh6hM0xj--