Summary: | libxcb (git version) fails to build | ||
---|---|---|---|
Product: | XCB | Reporter: | Jos van Wolput <wolput> |
Component: | Library | Assignee: | xcb mailing list dummy <xcb> |
Status: | RESOLVED FIXED | QA Contact: | xcb mailing list dummy <xcb> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jos van Wolput
2016-02-02 03:15:41 UTC
Did you update xcb/proto as well? The last commit in libxcb depends on the last commit of xcb/proto. Your build output looks like xcb/proto were not updated. (In reply to Christian Linhart from comment #1) > Did you update xcb/proto as well? > > The last commit in libxcb depends on the last commit of xcb/proto. > Your build output looks like xcb/proto were not updated. Fixed after updating xcb/proto. I don't think this bug is fixed; if xcb depends on a newer version of xcb-proto, the pkg-config dependency should reflect that. > --- Comment #3 from Josh Triplett <josh@freedesktop.org> ---
> I don't think this bug is fixed; if xcb depends on a newer version of
> xcb-proto, the pkg-config dependency should reflect that.
>
pkg-config shouldn't reflect build-time dependencies, this probably
belongs in configure.ac instead.
(In reply to Julien Cristau from comment #4) > > --- Comment #3 from Josh Triplett <josh@freedesktop.org> --- > > I don't think this bug is fixed; if xcb depends on a newer version of > > xcb-proto, the pkg-config dependency should reflect that. > > > pkg-config shouldn't reflect build-time dependencies, this probably > belongs in configure.ac instead. By "pkg-config dependency" here, I meant configure.ac's use of PKG_CHECK_MODULES with a ">= $VERSION". I'm saying that if libxcb needs a particular version of xcb-proto, it should have a versioned dependency on that version of xcb-proto. |
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.