On Tue, Nov 14, 2017 at 6:45 AM, Panu Matilainen <pmatilai@xxxxxxxxxx> wrote:
> On 11/14/2017 01:32 PM, Neal Gompa wrote:
>>
>> On Tue, Nov 14, 2017 at 2:07 AM, Florian Weimer <fweimer@xxxxxxxxxx>
>> wrote:
>>>
>>> On 11/14/2017 03:54 AM, Philip Kovacs wrote:
>>>>
>>>>
>>>> One concern is that -Wl,--as-needed requires greater accuracy with the
>>>> ordering of objects and
>>>> libraries as you link. Also, if a package uses a library indirectly,
>>>> i.e. A uses C via B: A -> B -> C,--as-needed will peel away C and break
>>>> A
>>>> unless A explicitly mentions its need for C.
>>>
>>>
>>>
>>> I think ld no longer links against symbols in indirect dependencies.
>>>
>>> #include <openssl/evp.h>
>>> int
>>> main()
>>> {
>>> return (int) &EVP_rc4;
>>> }
>>>
>>> /usr/bin/ld: /tmp/ccV4cmYY.o: undefined reference to symbol
>>> 'EVP_rc4@@OPENSSL_1_1_0'
>>> //usr/lib64/libcrypto.so.1.1: error adding symbols: DSO missing from
>>> command
>>> line
>>> collect2: error: ld returned 1 exit status
>>>
>>
>> I've only seen this with OpenSSL, so I think it's specific to that
>> library.
>>
>
> Implicit linking is not openssl specific at all, this is fairly old news by
> now as this change occurred in Fedora 13:
>
> https://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking
> https://fedoraproject.org/wiki/UnderstandingDSOLinkChange
Then something isn't working correctly, because then libcomps builds
should be failing in Fedora. It doesn't. It fails in *every other
Linux distribution* that I've built it for (Mageia, openSUSE,
OpenMandriva, Solus, and others...) unless I patch it to deliberately
link with zlib (it fails with similar issues noted with OpenSSL).
--
真実はいつも一つ！/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
