Re: linking rpm to already-installed libdb

[Jeff Johnson <jbj redhat com>]

On Thu, May 23, 2002 at 05:20:49PM -0400, Paul Jarc wrote:
> I'm installing rpm from source and I want to link to the popt and db
> libraries that I already have installed.  I seem to have rpm linked
> against the right popt, even though "make" still builds some of rpm's
> own popt sources as well.  No luck with db.
> 
> I found the --without-db option for configure, but it's not clear
> whether this is supposed to do what I want.  I tried it, and noticed
> that configure couldn't find db3/db.h, so I created a symlink "db3" ->
> "." in the db include directory.  (Assuming this is what configure is
> looking for, it would be better to look for plain db.h, at least if
> db3/db.h cannot be found, since db itself does not make db.h available
> as db3/db.h.)
> 
> That symlink let configure find db3/db.h, but I still get this error
> from make:
> Making all in rpmdb
> make[2]: Entering directory `/fs/home/mount/home/prj/src/sptools/rpm-4.0.3-1/rpmdb'
> make[2]: *** No rule to make target `../db3/db.h', needed by `dbconfig.lo'.  Stop.
> make[2]: Leaving directory `/fs/home/mount/home/prj/src/sptools/rpm-4.0.3-1/rpmdb'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/fs/home/mount/home/prj/src/sptools/rpm-4.0.3-1'
> make: *** [all-recursive-am] Error 2
> 
> Any ideas?  Should I be using --without-db at all?

Dunno. I added the switch just in case, no idea whether it woiks.

FWIW, part of the reason Berkeley DB was internalized was to make it
simpler to build rpm standalone, as there's a great deal of configuration
complexity in setting up Berkely DB. Any reason you can't use the
internal version? The symbols are already uniqified to prevent tool
chain pollution ...

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@redhat.com (jbj@jbj.org)
Chapel Hill, NC