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