Summary: | Include mismatch between 64bit & 32bit wayland-client-protocol.h | ||
---|---|---|---|
Product: | Wayland | Reporter: | Mike Lothian <mike> |
Component: | wayland | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | mike |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Build log |
Description
Mike Lothian
2013-07-08 22:56:34 UTC
That's a change in wayland master, but not a difference between 32 and 64 bit. I suspect you're comparing an older install of one set of headers on 32 bit to a newer set on 64 bit, or the other way around. This changed in wayland commit d94a8722cb29d8b897672be66ff3c9ff79eab6fe. Strange when I forced the install it worked great second time around - what's actually generating / pulling in this include. I notice it's not in the repository I'm using portage and it should be the same in both as both are being compiled together Created attachment 82203 [details]
Build log
Could it be because I'm not building the 32bit wayland-scanner and relying instead on the 64bit version?
|
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.