Hi there, On Tue, Dec 10, 2013 at 7:47 AM, Dominic Cleal <[email protected]> wrote: > Hi Chris, > > On 10/12/13 01:52, Chris Lalancette wrote: >> All, >> I'm pleased to announce the release of ruby-libvirt 0.5.0. ruby-libvirt >> is a ruby wrapper around the libvirt API. Version 0.5.0 brings new APIs, >> more >> documentation, and bugfixes: > > With ruby-libvirt 0.5.0, I'm now seeing compilation errors using Ruby > 1.8.7p371. Was dropping of 1.8 support in this update deliberate? > > gcc -I. -I. > -I/usr/local/rvm/rubies/ruby-1.8.7-p371/lib/ruby/1.8/x86_64-linux -I. > -DRUBY_EXTCONF_H=\"extconf.h\" -fPIC -g -O2 -fPIC -c common.c > common.c: In function ‘ruby_libvirt_typed_parameter_assign’: > common.c:385: error: ‘ST_CONTINUE’ undeclared (first use in this function) > common.c:385: error: (Each undeclared identifier is reported only once > common.c:385: error: for each function it appears in.) > common.c: In function ‘ruby_libvirt_set_typed_parameters’: > common.c:405: error: dereferencing pointer to incomplete type > make: *** [common.o] Error 1
No, it wasn't deliberate. Interesting, though; I thought that the ST_CONTINUE symbol existed in ruby 1.8. I'll take a look tonight and see if I can find where the problem is. Thanks for the report. Chris -- libvir-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/libvir-list
