* QA Notice: libsvn_client-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_delta-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_diff-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_fs-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_fs_base-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_fs_fs-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_ra-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_ra_dav-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_ra_local-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_ra_svn-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_repos-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_subr-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_swig_perl-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_swig_py-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_swig_ruby-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvn_wc-1.la appears to contain PORTAGE_TMPDIR paths * QA Notice: libsvnjavahl-1.la appears to contain PORTAGE_TMPDIR paths * * ERROR: dev-util/subversion-1.4.6-r1 failed. * Call stack: * misc-functions.sh, line 609: Called install_qa_check * misc-functions.sh, line 281: Called die * The specific snippet of code: * [[ ${abort} == "yes" ]] && die "soiled libtool library files found" * The die message: * soiled libtool library files found
Problem appears to be this line: ( emake external-all && emake LT_LDFLAGS="-L${D}/usr/$(get_libdir)" local-all ) || die "Compilation of ${PN} failed" It seems to build OK without the LT_LDFLAGS stuff.
Reopen with emerge --info and complete emerge log attached; this has been in the ebuild for months without anyone having such issues.
Created attachment 147062 [details] emerge.info
Created attachment 147065 [details] merge.log
attached
Don't see what this has to do with java. Add as us back if you can tell.
Do you still have this problem with Subversion 1.5.*?
