similar to: [PATCH 0/2] hivex: small portability fixes

These three patches ought to fix configure script detection of Ruby, especially on Debian where the Ruby C extensions library can be something like '-lruby1.8'. Rich.

This commit starts to split our massive, monolithic configure.ac file into smaller files, using the m4_include mechanism to combine them. I don't know if we should really do this, so I'm open to comments about it. However: - Our configure.ac script is 1800+ lines long, and that's pretty long. - configure.ac lacks structure; splitting it up might improve that. - From what I read,

Query RbConfig::CONFIG for "libdir", and use that when trying to link to the ruby library. This fixes the libruby detection when it is installed in a non-standard library directory. (This is the same change as 3d02e53c48266669675cc237f61ae2c4e1816e66 in libguestfs.) --- configure.ac | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac

Hi, continuing what started a couple of weeks ago [1], the attached patch series continues the work in making it easier to build and run libguestfs (in fixed appliance mode) on OSes different than Linux. The provided changes should cause no functional changes on Linux. [1] https://www.redhat.com/archives/libguestfs/2014-October/msg00176.html Thanks, -- Pino Pino Toscano (9): build: check

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a

I needed to add a few patches to be able to build libguestfs 1.20.2 out of tree. Mostly srcdir/builddir issues -- I think that I had posted something for building the daemon before. As mentioned on IRC, I found that compiling (Ruby bindings) caused config.h file shipped with the Ruby headers to be included rather than ${builddir}/config.h. This can be fixed because the relevant checks can be

(This is the same change as 87c9ec881cb695724e01d9f6fc9df996d4c67cb6 in libguestfs.) --- ruby/Makefile.am | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/ruby/Makefile.am b/ruby/Makefile.am index e78ab59..7a5fe42 100644 --- a/ruby/Makefile.am +++ b/ruby/Makefile.am @@ -45,13 +45,17 @@ all: $(RAKE) build $(RAKE) rdoc -RUBY_SITELIB := $(shell $(RUBY)

Here are three patches that fix issues with out-of-tree building and one that uses Ruby's own autoconf stuff for determining how Ruby bindings should be built. Cheers, -Hilko

Hi -- My book "Ruby for Rails" is now being released one chapter at a time through the Manning Early Access Program, with the whole book due to appear on May 1. If you''re interested, see http://www.manning.com/books/black (I guess I could have just sent my sig with no body, but anyway :-) David -- David A. Black (dblack@wobblini.net) Ruby Power and Light

I am trying to build wxruby from source, but I have encounter an error. For some reason the ''rake'' command fail when it tries to link lib/wxruby2.so because it is missing missing -lruby18 resulting in errors like wx.cpp:(.text+0x1618): undefined reference to `rb_intern'' wx.cpp:(.text+0x165c): undefined reference to `rb_eNotImpError'' wx.cpp:(.text+0x1666):

Hello, I'm attempting to create a Homebrew formula to get libguestfs to compile on Mac OS X. I've managed to achieve success with several monkey patches, but since Homebrew's policy is to contact maintainers about proper fixes in upstream, I would like to ask if there are any plans to fix these issues. I'm afraid I don't know C well enough to propose decent solutions myself.

Hi I''d like to put out a 1.9.3 release perhaps later this week/weekend. If you have a chance to test the build and samples esp with latest rubygems, please do. There are still some bugs on the list, and samples to do, but this should address all the build/install probs that have come up. And it would be good to get some testing and feedback on some of the new classes. A note on the

Hi, I''ve been using FFI with a Ruby 1.9.3 built with MSVC++ and it''s been working well. One thing I''ve run into though is this: ffi_lib :msvcrt But that''s not the runtime I want. But I don''t want to hard code the runtime name either. I realize I could parse it out of RbConfig, but I was hoping for something nicer. Is there a way we could create an

--- configure.ac | 4 +++- ruby/Makefile.am | 11 ++++++----- ruby/Rakefile.in | 2 +- ruby/run-bindtests | 2 +- ruby/run-ruby-tests | 4 ++-- 5 files changed, 13 insertions(+), 10 deletions(-) diff --git a/configure.ac b/configure.ac index ea0aec4..130db51 100644 --- a/configure.ac +++ b/configure.ac @@ -769,8 +769,10 @@ AC_ARG_ENABLE([ruby],

--- configure.ac | 15 +++++++++++++-- generator/generator.ml | 12 ++++++++++-- ruby/Makefile.am | 11 ++++++----- ruby/Rakefile.in | 2 +- ruby/run-ruby-tests | 4 ++-- 5 files changed, 32 insertions(+), 12 deletions(-) diff --git a/configure.ac b/configure.ac index 8651c7b..33c09db 100644 --- a/configure.ac +++ b/configure.ac @@ -312,8 +312,19 @@

Is rails + oci8 + mac os x intel a winning combination? It appears that oci8 might be a issue.

Add a --with-distro=ID argument for configure, so it is possible to manually specify the distro to use for the packages (in case os-release does not provide ID=.., or the ID is not recognized yet). In the case when --with-distro is not set, keep doing the autodetection, but using os-release only, i.e. dropping the checks for all the other -release files -- since there is --with-distro, older

Hi Heidi, Now We tried to install the puppet and puppet-server packages from puppetlabs, but we faced below discrepancy. Please look into this and let us know your suggestions because issue was not found in Puppet community as well. There was 1 issue related to this but it dint help us (http://projects.puppetlabs.com/issues/16634 ) We went through

This fixes the wxRED Mac link error. Thanks to Nick for pointing out that I hadn''t removed some wxRED code related to an earlier experiment. Hopefully this one will build on Mac, end-to-end. I also found and fixed a problem that was causing the crash on exit: wxWindows automatically deletes the C++ app object as soon as the last frame is closed. Later, when ruby garbage collected the

Gents, I installed ferret successfully in my MacOS (rails development) using the gem install. I did some tests and everything worked fine. Then I tried to install it on the same way on my production environment at TextDrive? running OpenSolaris? (container). This time ''gem install ferret'' seems to be completed: [92140-AA:~/web/labs/blogblogs/trunk] root# gem install ferret