I could prevent these collisions: /usr/lib32/libcurl.so.4.3.0 /usr/lib32/pkgconfig/libcurl.pc /usr/lib32/libcurl.so /usr/lib32/libcurl.so.4 by deleting the curl dependency in app-emulation/emul-linux-x86-baselibs-20140508-r11::personal and emerging curl following this new baselib.
app-emulation/emul-linux-x86-baselibs-20140508-r11::personal That's your own overlay, it seems.
of course I edit ebuild in my own: --- emul-linux-x86-baselibs-20140508-r11.ebuild 2014-06-15 21:01:05.000000000 +0200 +++ emul-linux-x86-baselibs-20140508-r11.ebuild 2014-06-16 10:16:00.000000000 +0200 @@ -93,7 +93,6 @@ >=net-libs/neon-0.30.0-r1[abi_x86_32(-)] >=dev-libs/nspr-4.10.6-r1[abi_x86_32(-)] >=dev-libs/nss-3.16-r1[abi_x86_32(-)] - >=net-misc/curl-7.37.0-r1[abi_x86_32(-)] ) >=sys-libs/glibc-2.16" # bug 340613 and could emerge the new curl before emul-linux-x86-baselibs ...
no, other way round ... latenight session for me in germany ...