Re: python3.9-config and rpath

["Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>]

Am Thu, 7 Jul 2022 05:52:22 +0000
schrieb nia <nia%NetBSD.org@localhost>:

> This seems good since it'll Just Work when used outside pkgsrc. If we
> take python-config to have the same guarantees as pkg-config, patching .pc
> scripts to add RPATH is already standard practice for us.

… with the added goodie of filtering out the rpath and lib paths again
if LD_RUN_PATH and LIBRARY_PATH are defined in the environment and
contain the paths already. This enables the world with no such
variables getting the explicit flags and the world that uses things
like environment modules to manage these path variables for differing
user development setups to benefit from these settings without a random
-rpath flag killing LD_RUN_PATH completely.

On the off-chance that you consider this worthwhile, as (incarnations
of) pkg-config already partly do so, in part at least, I wanted to have
this mentioned.

What I mean:

	https://github.com/pkgconf/pkgconf/blob/master/libpkgconf/client.c

	128: pkgconf_path_build_from_environ("LIBRARY_PATH", NULL, &client->filter_libdirs, false);

This adds directories to a list to drop -L flags for in the output. A
-config script might do the same, although it could be a nuisance to
code that everywhere. After all, that's why people create .pc files.

I need to revisit my discussion with pkgconf folks about also filtering
rpath args, not just -L. Right now, I just avoid -Wl,-R in the .pc
files I install with pkg-config (not quite sure right now, how).

Anyhow, just an idle thought about those -config scripts, too. Maybe
it's reasonable, if one has to patch them, to directly patch them to
just resort to a pkg-config call for that.


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg