| 1 |
On Mon, Jan 4, 2021 at 6:45 PM Mike Gilbert <floppym@g.o> wrote: |
| 2 |
> |
| 3 |
> On Mon, Jan 4, 2021 at 6:18 PM James Le Cuirot <chewi@g.o> wrote: |
| 4 |
> > $ PKG_CONFIG_SYSROOT_DIR=/foo pkg-config --variable=udevdir udev |
| 5 |
> > /lib/udev |
| 6 |
> > |
| 7 |
> > The udevdir variable is not affected by PKG_CONFIG_SYSROOT_DIR at all. |
| 8 |
> > And why would it be? The man page says that this variable is only |
| 9 |
> > applied to -I and -L flags. I don't know for sure but I suspect that |
| 10 |
> > pkg-config just sees this as some arbitrary variable with no special |
| 11 |
> > path handling at all. I wonder what led you to think that this fix was |
| 12 |
> > necessary? |
| 13 |
> |
| 14 |
> Interesting! |
| 15 |
> |
| 16 |
> pkg-config behaves differently on my system: |
| 17 |
> |
| 18 |
> % PKG_CONFIG_SYSROOT_DIR=/foo pkg-config --variable=udevdir udev |
| 19 |
> /foo/lib/udev |
| 20 |
> |
| 21 |
> This appears to be a difference in behavior between dev-util/pkgconfig |
| 22 |
> and dev-util/pkgconf. I am using pkgconf, and I would guess you are |
| 23 |
> using pkgconfig. |
| 24 |
> |
| 25 |
> I guess I will ask pkgconf upstream for help on this; it seems like |
| 26 |
> this is probably an unintended behavior. |
| 27 |
|
| 28 |
It seems that the pkgconf behavior is intentional. |
| 29 |
|
| 30 |
https://github.com/pkgconf/pkgconf/issues/69 |
| 31 |
|
| 32 |
I opened an issue to see if we can get some kind of opt-out. |
| 33 |
|
| 34 |
https://github.com/pkgconf/pkgconf/issues/205 |
Archives