1 |
2015-04-29 14:27 GMT+03:00 Anthony G. Basile <blueness@g.o>: |
2 |
|
3 |
> On 04/28/15 17:52, Mike Gilbert wrote: |
4 |
> |
5 |
>> On Tue, Apr 28, 2015 at 4:07 PM, Anthony G. Basile <blueness@g.o> |
6 |
>> wrote: |
7 |
>> |
8 |
>>> On 04/26/15 23:21, Duncan wrote: |
9 |
>>> |
10 |
>>>> Diego Elio Pettenò posted on Sun, 26 Apr 2015 17:41:04 +0100 as |
11 |
>>>> excerpted: |
12 |
>>>> |
13 |
>>>> On 25 April 2015 at 16:57, Duncan <1i5t5.duncan@×××.net> wrote: |
14 |
>>>>> |
15 |
>>>>> Of course, one thing that could make the process faster would be if |
16 |
>>>>>> C++ |
17 |
>>>>>> based packages were marked some way. |
18 |
>>>>>> |
19 |
>>>>> |
20 |
>>>>> revdep-rebuild --soname 'libstdc\+\+.so.*' |
21 |
>>>>> |
22 |
>>>>> should do the trick. Stuff that does not link the library (statically |
23 |
>>>>> linked or using libsupc++) should not really matter. |
24 |
>>>>> |
25 |
>>>> Thanks. Obvious in hindsight. =:^) |
26 |
>>>> |
27 |
>>>> just saw this. This works unless you have two versions of gcc |
28 |
>>> installed. |
29 |
>>> The c++11 abi emitted by gcc-4.7 and 4.8 are different and since you link |
30 |
>>> against the latest version (see the ordering of directories in |
31 |
>>> /etc/ld.so.conf.d/05gcc-x86_64-pc-linux-gnu.conf), building with the |
32 |
>>> earlier |
33 |
>>> gcc can cause breakage. We may not want to support such a situation but |
34 |
>>> I'd |
35 |
>>> like to. |
36 |
>>> |
37 |
>> As I understand it, a given version of gcc links objects against its |
38 |
>> own version of libstdc++, but the "latest" version of libstdc++ is |
39 |
>> loaded by ld.so at runtime. |
40 |
>> |
41 |
>> Maybe that's what you meant, but I wanted to clarify that. And if I am |
42 |
>> wrong on that, please correct me. ^_^ |
43 |
>> |
44 |
>> |
45 |
> Yes. So you could, for example, fix this by setting the correct rpath at |
46 |
> link time so the correct library gets loaded at runtime. |
47 |
|
48 |
|
49 |
I fear this discussion is going in a slightly wrong direction. I'm not |
50 |
going to make any global Gentoo changes, I just need to add support for |
51 |
C++14 mode in a bunch of packages I maintain, and for that, I need to |
52 |
decide on a place to store USE descriptions. If I won't get good options, |
53 |
I'll just go and add this description to every of ~70 metadata's. |
54 |
Please consider the patch I'm going to apply to our eclass: |
55 |
|
56 |
https://bpaste.net/show/39ec6f4760f4 |
57 |
|
58 |
This is intended as an experimental feature, not as a globally supported |
59 |
configuration for every package in Gentoo. This is needed because already |
60 |
now LeechCraft has some functionality that is implemented in C++14 and |
61 |
won't be available otherwise. |
62 |
|
63 |
Please give your opinion on where to put this USE desc, that's all I want :) |
64 |
|
65 |
|
66 |
> -- |
67 |
> Anthony G. Basile, Ph.D. |
68 |
> Gentoo Linux Developer [Hardened] |
69 |
> E-Mail : blueness@g.o |
70 |
> GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
71 |
> GnuPG ID : F52D4BBA |
72 |
> |
73 |
> |