On Sun, Jul 31, 2011 at 19:31, Jeff Johnson <n3...@mac.com> wrote: > > On Jul 31, 2011, at 6:21 PM, Robert Xu wrote: > >> >> Hm... >> I wanted to stay as close to the SuSE RPM spec as possible. >> And AFAICT that means that RPM uses an internal version of db… >> > Nothing wrong with that approach … checking … > > Its likely these 3 ./configure build options: > > • --with-db \ > • --with-dbsql \ > • --with-db-tools-integration \ > > Checking … try this instead: > > --with-db=internal \ > --with-dbsql=internal \ > --without-db-tools-integrated \ > > and double check that Berkeley DB is found by examining > the generated config.h looking for WITH_DB* settings there > > hth >> in the update spec file (http://slexy.org/view/s2yeaD531o) >> I actually have a copy of db5 and it is unpacked and symlinked to db/ >> So why isn't RPM picking up on it? >> > > Because I haven't bothered to look … ? > > Its quite clear what most users want is "system" Berkeley DB … my > own opinion is quite the opposite: if you want "system" Berkeley DB > then I ain't the one to ask for a "fix" that I don't believe in. > > Meanwhile what you are attempting is "internal" which I will help you sort > out. >
++ searching location: internal -- skipping not existing local sub-directory: db3 configure: error: unable to find internal Berkeley-DB library error: Bad exit status from /var/tmp/rpm-tmp.xXGIng (%build) that's... not supposed to happen, right? -- later, Robert Xu + rxu AT lincomlinux DOT org ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
