Date: Thu, 31 Jul 2014 04:08:08 +0200 From: Polytropon <freebsd@edvax.de> To: Brian Wood <woodbrian77@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Switching to newer version of Clang Message-ID: <20140731040808.7335de8f.freebsd@edvax.de> In-Reply-To: <CABWFOjsa98r1JvG4nVfiXqAB8epzSrfAaS-c15QogbUY2xiQfw@mail.gmail.com> References: <CABWFOjsa98r1JvG4nVfiXqAB8epzSrfAaS-c15QogbUY2xiQfw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140731040808.7335de8f.freebsd>