emerge dev-util/subversion Compilation fails: It depend on Berkeley DB, but the dependance was not installed before ! --------------------------------- checking for Apache module support via DSO through APXS... found at /var/tmp/portage/subversion-0.10_pre1/work/tmpinstall_httpd/bin/apxs checking for Berkeley DB in /var/tmp/portage/subversion-0.10_pre1/work/tmpinstall_db-4.0.14... no configure: error: Could not find Berkeley DB 4.0.14. !!! ERROR: dev-util/subversion-0.10_pre1 failed. !!! Function src_compile_svn, Line 145, Exitcode 1 !!! ./configure of subversion failed Reproducible: Always Steps to Reproduce: 1. 2. 3.
Still compiling, but seems it has passed the configure part. The Berkeley DB is no normal dependency, it is extracted and compiled during emerge (not installed as a package). Could you please sync again and retry? If it still fails, please provide a bit more information (like emerge info output).
Compiling went fine, on my system the installation is the problem - the apache files can't be copied. cp bails out saying: cp: failed to preserve ownership for /var/tmp/portage/subversion-0.10_pre1/image//usr/svn/lib/libapr.so.0: No such file or directory cp: failed to preserve ownership for /var/tmp/portage/subversion-0.10_pre1/image//usr/svn/lib/libaprutil.so.0: No such file or directory cp: failed to preserve ownership for /var/tmp/portage/subversion-0.10_pre1/image//usr/svn/lib/libaprutil.so: No such file or directory cp: failed to preserve ownership for /var/tmp/portage/subversion-0.10_pre1/image//usr/svn/lib/libapr.so: No such file or directory Could you please try if the ~x86 versions are more stable? :-)
Sorry, it still stops: (after "emerge sync") checking for Berkeley DB in /var/tmp/portage/subversion-0.10_pre1/work/tmpinstall_db-4.0.14... no configure: error: Could not find Berkeley DB 4.0.14. !!! ERROR: dev-util/subversion-0.10_pre1 failed. !!! Function src_compile_svn, Line 145, Exitcode 1 !!! ./configure of subversion failed
You still did not give the emerge info output... Another question: Please run ebuild /path/to/subversion/ebuild compile and give the output of ls /var/tmp/portage/subversion-0.10_pre1/work/tmpinstall_db-4.0.14/lib/
don't use subversion-0.10.x : it's very old and broken. try the new 0.21.0-r1 ebuild: it works fine (even if currently masked) and had ben recently (some days ago) subject to improvements and fixes
Why do portage keep this old ebuild, and make it default ? Isn't it possible to delete it, and make the new version unmasked ?
Karl, I think this should be masked. Any comments?
My problem in comment #2 is because of sandbox in FEATURES. cp -a does not work then.
Since this version is stinking, I've set it to ~arch and have added a warning in the ChangeLog. Perhaps someone still wants to try this, so I won't delete it for now, but it definitely is not stable. If someone wants to fix it, feel free to do so.