Re: Patching JSON tag without hardcoding library path (package firefox-pkcs11-loader)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il 05/03/2018 12:10, Florian Weimer ha scritto:
> On 03/05/2018 11:43 AM, Germano Massullo wrote:
>> Il 05/03/2018 08:25, Florian Weimer ha scritto:
>>> On 03/04/2018 03:02 PM, Germano Massullo wrote:
>>>> This tag is wrong and for example on x86_64 CPU architecture
>>>> systems, it
>>>> must be
>>>> "path": "/usr/lib64/pkcs11/onepin-opensc-pkcs11.so"
>>>>
>>>> How could I patch this file without having to hardcode the /usr/lib64
>>>> path?
>>>
>>> I'm not entirely sure what you mean, but if you install the library in
>>> /usr/lib or /usr/lib64 (say /usr/lib64/onepin-opensc-pkcs11.so), you
>>> can dlopen it using just its soname (onepin-opensc-pkcs11.so).
>>>
>> dlopen cannot be applied to my case
>
> How is the library loaded on a non-standard path, then?
>
> Thanks,
> Florian

Nikos, one of opensc maintainers replied to a my question about
onepin-opensc-pkcs11.so and LD path:

PKCS#11 modules in Fedora are not in LD path. The reason they are there
is that they are not generic libraries, but rather loadable modules.
Their location is "%{_libdir}/pkcs11"
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux