1 |
On 04/28/15 17:52, Mike Gilbert wrote: |
2 |
> On Tue, Apr 28, 2015 at 4:07 PM, Anthony G. Basile <blueness@g.o> wrote: |
3 |
>> On 04/26/15 23:21, Duncan wrote: |
4 |
>>> Diego Elio Pettenò posted on Sun, 26 Apr 2015 17:41:04 +0100 as excerpted: |
5 |
>>> |
6 |
>>>> On 25 April 2015 at 16:57, Duncan <1i5t5.duncan@×××.net> wrote: |
7 |
>>>> |
8 |
>>>>> Of course, one thing that could make the process faster would be if C++ |
9 |
>>>>> based packages were marked some way. |
10 |
>>>> |
11 |
>>>> revdep-rebuild --soname 'libstdc\+\+.so.*' |
12 |
>>>> |
13 |
>>>> should do the trick. Stuff that does not link the library (statically |
14 |
>>>> linked or using libsupc++) should not really matter. |
15 |
>>> Thanks. Obvious in hindsight. =:^) |
16 |
>>> |
17 |
>> just saw this. This works unless you have two versions of gcc installed. |
18 |
>> The c++11 abi emitted by gcc-4.7 and 4.8 are different and since you link |
19 |
>> against the latest version (see the ordering of directories in |
20 |
>> /etc/ld.so.conf.d/05gcc-x86_64-pc-linux-gnu.conf), building with the earlier |
21 |
>> gcc can cause breakage. We may not want to support such a situation but I'd |
22 |
>> like to. |
23 |
> As I understand it, a given version of gcc links objects against its |
24 |
> own version of libstdc++, but the "latest" version of libstdc++ is |
25 |
> loaded by ld.so at runtime. |
26 |
> |
27 |
> Maybe that's what you meant, but I wanted to clarify that. And if I am |
28 |
> wrong on that, please correct me. ^_^ |
29 |
> |
30 |
|
31 |
Yes. So you could, for example, fix this by setting the correct rpath |
32 |
at link time so the correct library gets loaded at runtime. |
33 |
|
34 |
-- |
35 |
Anthony G. Basile, Ph.D. |
36 |
Gentoo Linux Developer [Hardened] |
37 |
E-Mail : blueness@g.o |
38 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
39 |
GnuPG ID : F52D4BBA |