Summary: | libxcb fails to build with xorgproto, a python is failing | ||
---|---|---|---|
Product: | XCB | Reporter: | n3rdopolis <bluescreen_avenger> |
Component: | Library | Assignee: | xcb mailing list dummy <xcb> |
Status: | RESOLVED INVALID | QA Contact: | xcb mailing list dummy <xcb> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
n3rdopolis
2018-02-09 03:22:20 UTC
This looks like the second report we've received related to the generic event support in xorgproto? Does someone want to revert that functionality until we can get sorted out what is up? Should I? Or is there something I'm missing? (In reply to Bart Massey from comment #1) > This looks like the second report we've received related to the generic > event support in xorgproto? Does someone want to revert that functionality > until we can get sorted out what is up? Should I? Or is there something I'm > missing? Building libxcb master against the split protocol packages fails the same way (verified on Fedora 27). So this is not a bug with xorgproto, this is a bug with the generic event support. Can someone tell me what building libxcb has to do with xorgproto? I thought it only uses the XML and Python files from xcb/proto...? (Disclaimer: I have not heard of this new xorgproto repository before and I am quite certain that there was no mail on the xcb mailing list about it) Close this, I am sorry, I needed to build a more recent version of the 'proto' repository |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.