Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#49749 - [lib32-gtk3] Should it be built with PKG_CONFIG_LIBDIR instead of PKG_CONFIG_PATH?

Attached to Project: Community Packages
Opened by Alexandre Bique (babali) - Friday, 17 June 2016, 10:55 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 17 June 2016, 12:59 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hi,

I looked into lib32-gtk3 PKGBUILD, and I found that it is using PKG_CONFIG_PATH.

But when I tried to compile a program using lib32-gtk3 and using PKG_CONFIG_LIBDIR=/usr/lib/pkgconfig then I got complain that xproto was not available.

So is it possible that the current build of lib32-gtk3 is using the 64 bits xproto package?

Note: As I understand, PKG_CONFIG_PATH adds new path to pkg config, while PKG_CONFIG_LIBDIR? replaces all of them so really restricts to what is in /usr/lib32/.

Should we build lib32* with PKG_CONFIG_PATH or PKG_CONFIG_LIBDIR?

Thank you.
Regards,
Alexandre
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 17 June 2016, 12:59 GMT
Reason for closing:  Not a bug
Additional comments about closing:  xproto isn't architecture specific.

Loading...