Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030203 Description of problem: ./configure is looking for libdb3 or libdb-3, neither of which is found in phoebe or rawhide. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. rpmbuild --rebuild php-4.2.2-15.src.rpm 2. 3. Actual Results: After running ./configure ... checking for db_create in -ldb... no checking for db_create in -ldb-3... no checking for db_create in -ldb3... no configure: error: cannot find necessary library error: Bad exit status from /var/tmp/rpm-tmp.80673 (%build) Expected Results: Profit! Additional info: One line fix to resolve: --- php.spec 2003-02-10 09:13:10.000000000 -0600 +++ php.spec.dj3 2003-02-12 07:35:59.000000000 -0600 @@ -256,7 +256,7 @@ --disable-rpath \ --enable-inline-optimization \ --with-bz2 \ - --with-db3 \ + --with-db \ --with-curl \ --with-dom=%{_prefix} \ --with-exec-dir=%{_bindir} \
The above makes php compile, but does not permit php to use db functions. Do not use the above. Appending "-ldb -lpthread" to LIBS (in the .spec) may work.
Latest/stable php (4.3.0) compiles fine. (this may be preferable to the ugly cludge listed above).
Do you have the db4-devel package installed? db_create should be found in the -ldb provided by db4-devel. Can you attach the build-cgi/config.log produced a --rebuild which failed as above?
Created attachment 90068 [details] Config.log file from a failed build Yes, I do have db4-devel-4.0.14-18 installed. The above attachment is from "% rpmbuild --rebuild php-4.2.2-16.src.rpm"
Curious. I can link against -ldb without needing -lpthread on my Phoebe system. You're also using CC=/usr/local/bin/gcc - have you tried CC=/usr/bin/gcc? Or maybe the -18 db4 package breaks this.
Yeah, looks like this was a transient breakage in db4-devel. *** This bug has been marked as a duplicate of 83434 ***
Just FYI, I'm using /usr/local/bin/gcc to take advantage of ccache. (It simply caches from gcc-3.2.1-7)
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.