From owner-freebsd-questions@FreeBSD.ORG Thu Jul 31 02:08:19 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4AABC31 for ; Thu, 31 Jul 2014 02:08:19 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 66D4123EA for ; Thu, 31 Jul 2014 02:08:18 +0000 (UTC) Received: from r56.edvax.de (port-92-195-69-249.dynamic.qsc.de [92.195.69.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id E220B3CBC9; Thu, 31 Jul 2014 04:08:08 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s6V288BR005867; Thu, 31 Jul 2014 04:08:08 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 31 Jul 2014 04:08:08 +0200 From: Polytropon To: Brian Wood Subject: Re: Switching to newer version of Clang Message-Id: <20140731040808.7335de8f.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 02:08:19 -0000 On Wed, 30 Jul 2014 21:01:07 -0500, Brian Wood wrote: > I did a make install in > > /usr/ports/devel/llvm34 > > After it finished > > clang -v > > still says 3.3. Do I have to reboot or try something > different? Thanks. Which OS version are you using? If I remember correctly, on v10 clang has replaced the classic GCC toolset. That's why $ which clang will probably tell you that your above command has called the system's clang which didn't change. The installed port now provides a _second_ clang binary at a different path, probably somewhere in /usr/local, and maybe the binary has a version suffix (similar to gcc from ports). What does $ which clang3.4 report? Just check the installed files for the llvm port, you'll quickly find the correct name of the clang binary. I don't have a v10 system to access at the monent, so I cannot check, sorry; still on v8.2 at home, no clang. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...