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#64532 - [tigervnc] SHIT DOESN'T COMPILE DUE TO STUPIDITY ABOUT GLPROTO VERSION
Attached to Project:
Community Packages
Opened by Sp1d3rmxn (sp1d3rmxn) - Saturday, 16 November 2019, 10:33 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 27 December 2019, 09:21 GMT
Opened by Sp1d3rmxn (sp1d3rmxn) - Saturday, 16 November 2019, 10:33 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 27 December 2019, 09:21 GMT
|
DetailsDescription:
Shit doesn't build in chroot or outside of it on fresh install on 4 different machines. configure: error: Package requirements (glproto >= 1.4.17 gl >= 9.2.0) were not met: Package dependency requirement 'gl >= 9.2.0' could not be satisfied. Package 'gl' has version '1.2', required version is '>= 9.2.0' Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GL_CFLAGS and GL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ==> ERROR: A failure occurred in build(). Aborting... Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: makechrootpkg or makepkg (add flags as you see fit doesn't matter shit doesn't compile). |
This task depends upon
Installed the trunk version of Xorg-server that contains that patch and it still fails. I am able to force it to try by doing "GL_CFLAGS=9.2.0 GL_LIBS=9.2.0 makepkg".
It doesn't complete but, it gets closer.
Should I request closure for this or not really since the current PKGBUILD is not actually correctly reflecting these necessary changes?
The package is flagged outdated for nearly two months now and has problems in the current build with proxmox. Can somebody please fix this and release an updated package?
Thank you.