| 1 |
On 02/21/2015 12:18 PM, Zac Medico wrote: |
| 2 |
> On 02/21/2015 08:14 AM, Anthony G. Basile wrote: |
| 3 |
>> Finally, a limitation of the above should be noted. Since the |
| 4 |
>> CFLAGS/CXXFLAGS cached are only those supplied by the user, it does not |
| 5 |
>> cover situations where the package build system or ebuild supply their |
| 6 |
>> own -std= flag. Since this information cannot and should not be cached |
| 7 |
>> by the package manager, utilities used to find any mismatches in C++ ABI |
| 8 |
>> must provide for this intelligence. |
| 9 |
> |
| 10 |
> I wonder if it's feasible to force the -rpath option when using the |
| 11 |
> -std= flag, and force the real/canonical libstc++.so path into the |
| 12 |
> rpath. There's some mention of -rpath here: |
| 13 |
> |
| 14 |
> http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN95 |
| 15 |
> |
| 16 |
> Have the -rpath information in the binaries should make it easy to |
| 17 |
> correctly resolve the library dependencies. |
| 18 |
|
| 19 |
If we put the real/canonical libstdc++.so path in the DT_NEEDED section, |
| 20 |
then it will automatically work with existing soname dependency support. |
| 21 |
-- |
| 22 |
Thanks, |
| 23 |
Zac |
Archives