Hi Ingvar,
On Thursday, March 28, 2019 11:58:21 AM CET Ingvar Hagelund wrote:
> Fedora prohibits the use of rpath, ref
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
>
> When compiling varnish with litbool, I ensure this by the usual
>
> sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g;
> s|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool
With new enough libtool script, you can use this instead:
%configure LT_SYS_LIBRARY_PATH=%_libdir
or if that makes sense in your case:
%configure LT_SYS_LIBRARY_PATH=%_libdir:
This is unfortunately needed because it is not easy to detect whether the
linker uses /usr/lib64 path by default. Ideas? Libtool attempts to parse
ld.so.conf & friends, but the desired info isn't there....
> However, during build and check, I need access to a library in the build. For
> example, the test suite uses the binary varnishtest to access
> libvarnishapi.so.2, which is not visible as the package is not installed yet.
If you use the LT_SYS_LIBRARY_PATH instead DIE_RPATH_DIE the tests should
just work.
> I have gotten around this by putting in LD_LIBRARY_PATH where I need,
> but rpmlint gives me a warning on that.
Can you post the warnings? I've been using LD_LIBRARY_PATH in %check for
quite some time [1], and rpmlint did not complain...
> Are there other possibilities to solve this?
Report that to rpmlint so they don't complain in %check? Push to rpmlint
upstream to implement ignore file?
[1]
https://src.fedoraproject.org/rpms/libarchive/c/f64e33e456d935e34f6202449cecb9eb00136436?branch=master
Pavel
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
