| Summary: | Subversion emerge fails, says cannot find Berkley DB 4.0.14, but epm reports it is installed. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tom Wigington <gentoo> |
| Component: | [OLD] Development | Assignee: | Paul de Vrieze (RETIRED) <pauldv> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | drakos7, sigbjorn, tobias |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | /var/tmp/portage/subversion-1.0.4-r1/work/subversion-1.0.4/config.log | ||
|
Description
Tom Wigington
2004-06-11 07:59:44 UTC
Please attach /var/tmp/portage/subversion-1.0.4-r1/work/subversion-1.0.4/config.log Created attachment 33098 [details]
/var/tmp/portage/subversion-1.0.4-r1/work/subversion-1.0.4/config.log
I see the same behaviour here with db4.2. It seems the build fails if there is a newer/different version of db installed than that used for apache/apr-util. The failure in the build/ac-macros/berkeley-db.m4 looks very similar to bug 46936. Due to my limited knowledge I failed to "port" the solution from Max Kalika to be found in /usr/portage/dev-libs/cyrus-sasl/files/cyrus-sasl-2.1.18-db4.patch. You are right, unless unavoidable, use the same version on apr/apu and subversion. From my tests it seems that 4.2 does not work reliable in any case, but that could be caused my versioning conflicts ok .. I unmerged db-4.2* and I was able to build subversion .. this is still current for latest version of subversion maybe subversion should block db-4.2* .. Subversion actually wants to link against the db version that your apache libraries were linked against. To fix this you can remerge your apache. I'll look at adding a check for this that explains this situation. what if we cannot re-emerge apache? It is bombing out on me with stuff like: /var/tmp/portage/apache-2.0.52-r1/work/httpd-2.0.52/srclib/apr/.libs/libapr-0.so: undefined reference to 'pthread_create'. Is this a "/sbin/fix_libtool_files.sh" issue? *** Bug 65986 has been marked as a duplicate of this bug. *** Greg, the pthread thing is probably a glibc issue. Hopefully remerging that will solve your apache recompilation problem. If you want another way, please attach your config.log. You could also try to change apu-config to use -ldb-4.0 instead of -ldb. Thanks Paul. Recompiling glibc got me past that hurdle. I had the same problem (1.1.4 and 1.2.0), spent hours on it today. For some reason I'd set "-berkdb -gdbm" for apr-util in packages.keywords, removing that solved the problem for me. I don't know much about ebuilds - is it possible to make portage check whether a specific package has been built with specific use flags? Re-emerge apr/apr-util... *** This bug has been marked as a duplicate of 114481 *** |