Summary: | app-emulation/libvirt compilation fails. Errors related to yajl library. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gerard Garcia <nouboh> |
Component: | [OLD] Library | Assignee: | Matthias Maier <tamiko> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | cardoe, virtualization |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/gentoo/gentoo/pull/1083 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Gerard Garcia
2016-03-14 11:46:31 UTC
what version of yajl do you have? 2.0.4-r3 Could be related to the fact that our 2.x series is pretty out of date. You could try a 1.x series of yajl. I've submitted fixes to update our 2.x. With version 1.0.11-r1 libvirt compiles correctly. Maybe libvirt should enforce installation of a 1.x version. (In reply to Gerard Garcia from comment #4) > With version 1.0.11-r1 libvirt compiles correctly. Maybe libvirt should > enforce installation of a 1.x version. dev-libs/yajl-2.0.4-r3 has been stabilized around Dec 27 2014. We have successfully compiled a lot of libvirt versions against yajl since then. I think something else is the problem. Maybe there are some yajl-1* remnants on your system and libvirt gets confused by that... (In reply to Gerard Garcia from comment #4) > With version 1.0.11-r1 libvirt compiles correctly. Maybe libvirt should > enforce installation of a 1.x version. I've recently added 2.1.0 to the tree. Do you mind retesting with that? libvirt source code checks if you're on 1.x or 2.x and its possible they now use some of the 2.1.0 bits if they're on 2.x. (In reply to Matthias Maier from comment #5) > (In reply to Gerard Garcia from comment #4) > > With version 1.0.11-r1 libvirt compiles correctly. Maybe libvirt should > > enforce installation of a 1.x version. > > dev-libs/yajl-2.0.4-r3 has been stabilized around Dec 27 2014. > We have successfully compiled a lot of libvirt versions against yajl since > then. > > > I think something else is the problem. Maybe there are some yajl-1* remnants > on your system and libvirt gets confused by that... Well, you were right. I had some old yajl headers in /usr/local/include that were confusing libvirt. (In reply to Doug Goldstein from comment #6) > (In reply to Gerard Garcia from comment #4) > > With version 1.0.11-r1 libvirt compiles correctly. Maybe libvirt should > > enforce installation of a 1.x version. > > I've recently added 2.1.0 to the tree. Do you mind retesting with that? > libvirt source code checks if you're on 1.x or 2.x and its possible they now > use some of the 2.1.0 bits if they're on 2.x. After removing these headers, libvirt compiles without problems with yajl 2.1.0. Thanks! (In reply to Gerard Garcia from comment #7) > (In reply to Matthias Maier from comment #5) > > (In reply to Gerard Garcia from comment #4) > > > With version 1.0.11-r1 libvirt compiles correctly. Maybe libvirt should > > > enforce installation of a 1.x version. > > > > dev-libs/yajl-2.0.4-r3 has been stabilized around Dec 27 2014. > > We have successfully compiled a lot of libvirt versions against yajl since > > then. > > > > > > I think something else is the problem. Maybe there are some yajl-1* remnants > > on your system and libvirt gets confused by that... > > Well, you were right. I had some old yajl headers in /usr/local/include that > were confusing libvirt. Ah ok. Since it was something local to your machine I'm going to close as invalid. Glad everything is working now, let us know if any other issues come up. |