Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#72378 - [xtrans][xorg-util-macros] .pc files maybe needs install in architecture agnostic path

Attached to Project: Arch Linux
Opened by Gustavo Alvarez (sl1pkn07) - Sunday, 10 October 2021, 02:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



the .pc files in both packages install the .pc files in /usr/lib

due is a headers only/set defines packages, this .pc files maybe set installed in archtitecture agnostic path, like /usr/share/pkgconfig

in the packagebuidls have this lines added 13/11y ago

maybe need remove and leave untouched the upstream behavior


This task depends upon

Comment by Andreas Radke (AndyRTR) - Sunday, 10 October 2021, 18:49 GMT
andyrtr@workstation64:[/tmp/luit/trunk]$ find /usr/lib/pkgconfig/ | wc -l
andyrtr@workstation64:[/tmp/luit/trunk]$ find /usr/share/pkgconfig/ | wc -l

Afaik there's no strict rule from FHS but in the recent years files moved over /usr/lib.
Comment by Gustavo Alvarez (sl1pkn07) - Sunday, 10 October 2021, 18:53 GMT
and what happen with multilib builds when use headers-only package?. 32builds .pc files is stored in /usr/lib32/pkgconfig. no interfiere when that build search that pkgfiles when use PKG_CONFIG_PATH="/usr/lib32/pkgconfig"?

Comment by Jan Alexander Steffens (heftig) - Tuesday, 12 October 2021, 23:39 GMT
Using PKG_CONFIG_PATH="/usr/lib32/pkgconfig" still leaves /usr/lib/pkgconfig in the search path, so it would work but this is wrong. You should be using PKG_CONFIG="i686-pc-linux-gnu-pkg-config" instead, which properly switches out lib with lib32. In that case, we do need architecture-independent stuff in /usr/share/pkgconfig.
Comment by Gustavo Alvarez (sl1pkn07) - Wednesday, 13 October 2021, 00:19 GMT

PKG_CONFIG="i686-pc-linux-gnu-pkg-config" is it used in any arch packages at the moment? because PKG_CONFIG_PATH="/usr/lib32/pkgconfig" is how arch package guidelines dict

Comment by Jan Alexander Steffens (heftig) - Wednesday, 13 October 2021, 00:29 GMT
I've never seen those lib32 guidelines before. They're simply wrong, and not just on the pkg-config issue.