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!
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!
FS#36002 - [libxcb, xcb-proto] No need to force PYTHON=/usr/bin/python2, libxcb/xcb-proto build OK with python3
Attached to Project:
Arch Linux
Opened by Alain Kalker (ackalker) - Tuesday, 02 July 2013, 19:25 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 23 July 2013, 11:12 GMT
Opened by Alain Kalker (ackalker) - Tuesday, 02 July 2013, 19:25 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 23 July 2013, 11:12 GMT
|
DetailsDescription:
As suggested[1] by Daniel Martin: libxcb and xcb-proto should build with python3 now. I've tested this by building xcb-proto and libxcb with PYTHON= line removed from both PKGBUILDs, and the packages build and install normally. It is even possible to build libxcb using python3 while xcb-proto built with python2 is still installed (libxcb will refer to the correct installation directory used by xcb-proto, neat!) [1]: https://bugs.freedesktop.org/show_bug.cgi?id=66413#c15 Additional info: * package version(s) libxcb 1.9.1-1 xcb-proto 1.8-1 * config and/or log files etc. Steps to reproduce: |
This task depends upon