1 |
On 17-04-10 at 20:48, Andrew Lowe wrote: |
2 |
> On 10/04/17 18:57, J. Roeleveld wrote: |
3 |
> > On April 10, 2017 12:41:54 PM GMT+02:00, Andrew Lowe <agl@×××××××.au> wrote: |
4 |
> >> On 10/04/17 18:08, Neil Bothwick wrote: |
5 |
> >>> On Mon, 10 Apr 2017 17:13:28 +0800, Andrew Lowe wrote: |
6 |
> >>> |
7 |
> >>>> Do we have any clang users out there? I've had clang installed |
8 |
> >>>> on my machine for ages and a simple "clang test.c" will result in an |
9 |
> >>>> executable. I can even nearly build my whole machine using clang, so |
10 |
> >>>> its up and running. I've now just updated clang, from a working |
11 |
> >> 3.9.1 |
12 |
> >>>> to a 4.0.0-r1 and clang has now disappeared. If I type in "clang |
13 |
> >>>> --version", I get "command not found". "whereis clang" only gives me |
14 |
> >>>> the library dir. Doing "ls -la /usr/bin/cla*" gives me "No such file |
15 |
> >> or |
16 |
> >>>> directory" |
17 |
> >>> |
18 |
> >>> Try "qlist clang" so see what is installed, "qlist clang | grep bin/" |
19 |
> >>> should find the executables. |
20 |
> >>> |
21 |
> >>> qlist is part of portage-utils, which you probably already have. |
22 |
> >>> |
23 |
> >>> |
24 |
> >> |
25 |
> >> Done as requested. There are 41 files found with clang in their name |
26 |
> >> and they are all on the dir: |
27 |
> >> |
28 |
> >> /usr/lib/llvm/4/bin/ |
29 |
> >> |
30 |
> >> I'm no whiz bang sys-admin but that doesn't seem right to me. There is |
31 |
> >> |
32 |
> >> clang and clang++ and a whole lot of stuff sym linked to provide all |
33 |
> >> the |
34 |
> >> various permutations and combinations of names in there. But there is |
35 |
> >> nothing in my path that points to that dir. I'll have to have a look at |
36 |
> >> |
37 |
> >> the ebuild to see if a symlink or something is not being applied. |
38 |
> >> |
39 |
> >> Any other thoughts appreciated, |
40 |
> >> |
41 |
> >> Andrew |
42 |
> > |
43 |
> > Try those and see if they respond correctly. |
44 |
> > If yes, add that dir to your PATH. |
45 |
> > |
46 |
> > -- |
47 |
> > Joost |
48 |
> > |
49 |
> |
50 |
> They work as expected and I can add the dir to the path with no |
51 |
> problems, I'm more concerned about why I have add the path - is the |
52 |
> ebuild screwed up in some way? |
53 |
> |
54 |
> What is the portage/ebuild doco like? Is it well documented or are |
55 |
> there gaping holes that lead to frustration - my level of understanding |
56 |
> of coding is 25 years of C/C++ coding on CAD systems & engineering |
57 |
> applications and even though I run a Gentoo box as my default machine, |
58 |
> I've never had the need to get into bash scripting - but might. |
59 |
> |
60 |
> Andrew |
61 |
> |
62 |
|
63 |
Try running `env-update && source /etc/profile'. Your path should be |
64 |
extended by /etc/profile.env which is generated from /etc/env.d/10llvm-9995. |
65 |
|
66 |
-- |
67 |
Simon Thelen |