If you have both db4-devel.x86_64 and db4-devel.i386 installed on an x86_64
system, and you have /usr/lib/libdb-4.x.la, the build (libtool) will attempt to
link with /usr/lib/libdb-4.x.so instead of /usr/lib64/libdb-4.x.so.
Created attachment 233041 [details]
Created attachment 233071 [details]
cvs commit log
Reviewed by: nhosoi (Thanks!)
Fix Description: Once again, libtool attempts to be helpful but is instead
harmful. If you have both db4-devel.i386 and db4-devel.x86_64 installed, this
will install /usr/lib/libdb-4.N.la. If you use libtool to link with -ldb-4.N,
and you do not specify a search path, libtool will attempt to find this library
in it's default search path, which is something like
/usr/lib/gcc/x86_64/blahblahblah/../../../lib. This will find
/usr/lib/libdb-4.N.la and will use the information in that file and link the
object with /usr/lib/libdb-4.N.so, instead of just passing -ldb-4.N through to
the linker which is what it ought to do (darn libtool). In order to make
libtool do the right thing, we must pass in -L$libdir -ldb-4.N to libtool so
that it will use $libdir first in its search path.
Platforms tested: RHEL5 x86_64, RHEL4 x86_64
Flag Day: yes - autotool file changes
Doc impact: no
Verified. DS builds fine on RHEL5 x86_64 if both db4-devel.i386 and
db4-devel.x86_64 are installed.