On Tue, Aug 28, 2012 at 4:19 AM, Peter Krempa wrote:
> On 08/27/12 23:09, Eric Blake wrote:
>> On 08/24/2012 10:19 AM, Eric Blake wrote:
>>
>>> Ah, that rings a bell, I knew I'd seen this issue before. I'm actually
>>> surprised it STILL hasn't been fixed in Ubuntu, and maybe it's time to
>>> app
On 08/27/12 23:09, Eric Blake wrote:
> On 08/24/2012 10:19 AM, Eric Blake wrote:
>
>> Ah, that rings a bell, I knew I'd seen this issue before. I'm actually
>> surprised it STILL hasn't been fixed in Ubuntu, and maybe it's time to
>> apply the workaround below as a build-breaker fix (I think I've
On 08/24/2012 10:19 AM, Eric Blake wrote:
> Ah, that rings a bell, I knew I'd seen this issue before. I'm actually
> surprised it STILL hasn't been fixed in Ubuntu, and maybe it's time to
> apply the workaround below as a build-breaker fix (I think I've posted
> it on list before, but never commi
On 08/24/2012 04:02 PM, Eric Blake wrote:
> On 08/24/2012 01:54 PM, Laine Stump wrote:
Thomas, do you have any info on the libnl version used in Ubuntu 10.04,
and/or what might be the cause of this warning.
>>> It's a static inline which I guess is the problem here. Laine, you
>>> are pro
On 08/24/2012 01:54 PM, Laine Stump wrote:
>>> Thomas, do you have any info on the libnl version used in Ubuntu 10.04,
>>> and/or what might be the cause of this warning.
>> It's a static inline which I guess is the problem here. Laine, you
>> are probably using a libnl version which does not inclu
On 08/24/2012 11:49 AM, Thomas Graf wrote:
> On Fri, Aug 24, 2012 at 11:30:44AM -0400, Laine Stump wrote:
>> On 08/24/2012 10:28 AM, Viktor Mihajlovski wrote:
>>> fwiw ... with the current GIT level I get the following build error on
>>> Ubuntu 10.04 32-bit
>>>
>>> CC libvirt_util_la-virnetdev
On 08/24/2012 09:49 AM, Thomas Graf wrote:
> It's a static inline which I guess is the problem here. Laine, you
Actually, Viktor hit the problem; Laine couldn't reproduce, so it is
probably Viktor with the older header.
> are probably using a libnl version which does not include the commit
> belo
On Fri, Aug 24, 2012 at 11:30:44AM -0400, Laine Stump wrote:
> On 08/24/2012 10:28 AM, Viktor Mihajlovski wrote:
> >
> > fwiw ... with the current GIT level I get the following build error on
> > Ubuntu 10.04 32-bit
> >
> > CC libvirt_util_la-virnetdev.lo
> > cc1: warnings being treated as err
On 08/24/2012 10:28 AM, Viktor Mihajlovski wrote:
>
> fwiw ... with the current GIT level I get the following build error on Ubuntu
> 10.04 32-bit
>
> CC libvirt_util_la-virnetdev.lo
> cc1: warnings being treated as errors
> /usr/include/netlink/object.h:58: error: inline function 'nl_object_p
On 08/24/2012 08:28 AM, Viktor Mihajlovski wrote:
> fwiw ... with the current GIT level I get the following build error on Ubuntu
> 10.04 32-bit
>
> CC libvirt_util_la-virnetdev.lo
> cc1: warnings being treated as errors
> /usr/include/netlink/object.h:58: error: inline function 'nl_object_p
On 08/22/2012 01:51 PM, Daniel Veillard wrote:
>As planned, I just tagged 0.10.0 release candidate 1 in git and
> pushed a tarball and rpms to the usual place:
> ftp://libvirt.org/libvirt/
>
> I gave it a try locally and things seems to work as expected, but
> that's far from an extensiv
As planned, I just tagged 0.10.0 release candidate 1 in git and
pushed a tarball and rpms to the usual place:
ftp://libvirt.org/libvirt/
I gave it a try locally and things seems to work as expected, but
that's far from an extensive testing :-)
So please try it, try to compile it on variou
12 matches
Mail list logo
