[chef] Re: Omnibus health check failing because of libdb


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: Omnibus health check failing because of libdb
  • Date: Fri, 17 Jan 2014 15:31:10 -0800


On Friday, January 17, 2014 at 3:22 PM, lharms wrote:

Howdy,

I didn't find an Omnibus mailing list so hopefully it is ok to bring it
up here. If not, let me know.

I've tried building several package with ruby and always get the same
result. The health check fails because of the unsafe/unmet dependencies
of /lib64/libdb-4.7.so.

I get this error using the omnibus-software files. I've also tried
writing a Berkeley DB dependency and still get the same error.

Alas my dependency-fu is weak. Can someone point me in the right
direction?

A full error message is available at:

Thanks,
Lucas
What are you doing differently than https://github.com/opscode/omnibus-software/blob/master/config/software/ruby.rb ? What build platform is this (linux/other, distro, etc.)?

The general solution for these kinds of issues is to modify the arguments to configure to either disable a component if you don’t want it, or pass in an option that will make the compiler link to your embedded library if you do want that component (or there’s no option to disable it).

-- 
Daniel DeLeo




Archive powered by MHonArc 2.6.16.

§