On 10/04/17 18:57, J. Roeleveld wrote:
On April 10, 2017 12:41:54 PM GMT+02:00, Andrew Lowe <a...@wht.com.au> wrote:
On 10/04/17 18:08, Neil Bothwick wrote:
On Mon, 10 Apr 2017 17:13:28 +0800, Andrew Lowe wrote:
Do we have any clang users out there? I've had clang installed
on my machine for ages and a simple "clang test.c" will result in an
executable. I can even nearly build my whole machine using clang, so
its up and running. I've now just updated clang, from a working
3.9.1
to a 4.0.0-r1 and clang has now disappeared. If I type in "clang
--version", I get "command not found". "whereis clang" only gives me
the library dir. Doing "ls -la /usr/bin/cla*" gives me "No such file
or
directory"
Try "qlist clang" so see what is installed, "qlist clang | grep bin/"
should find the executables.
qlist is part of portage-utils, which you probably already have.
Done as requested. There are 41 files found with clang in their name
and they are all on the dir:
/usr/lib/llvm/4/bin/
I'm no whiz bang sys-admin but that doesn't seem right to me. There is
clang and clang++ and a whole lot of stuff sym linked to provide all
the
various permutations and combinations of names in there. But there is
nothing in my path that points to that dir. I'll have to have a look at
the ebuild to see if a symlink or something is not being applied.
Any other thoughts appreciated,
Andrew
Try those and see if they respond correctly.
If yes, add that dir to your PATH.
--
Joost
They work as expected and I can add the dir to the path with no
problems, I'm more concerned about why I have add the path - is the
ebuild screwed up in some way?
What is the portage/ebuild doco like? Is it well documented or are
there gaping holes that lead to frustration - my level of understanding
of coding is 25 years of C/C++ coding on CAD systems & engineering
applications and even though I run a Gentoo box as my default machine,
I've never had the need to get into bash scripting - but might.
Andrew
