Onigurama being http://www.geocities.jp/kosako3/oniguruma/ . Symbol onig_alloc_init@@ (64-bit UNIX System V ABI AMD x86-64 architecture) present 3 times /usr/lib64/php5/bin/php-cgi /usr/lib64/php5/bin/php /usr/lib64/libruby18.so.1.8.6 Symbol onig_bbuf_init@@ (64-bit UNIX System V ABI AMD x86-64 architecture) present 3 times /usr/lib64/php5/bin/php-cgi /usr/lib64/php5/bin/php /usr/lib64/libruby18.so.1.8.6 Symbol onig_chain_reduce@@ (64-bit UNIX System V ABI AMD x86-64 architecture) present 3 times /usr/lib64/php5/bin/php-cgi /usr/lib64/php5/bin/php /usr/lib64/libruby18.so.1.8.6 Symbol onig_compile@@ (64-bit UNIX System V ABI AMD x86-64 architecture) present 3 times /usr/lib64/php5/bin/php-cgi /usr/lib64/php5/bin/php /usr/lib64/libruby18.so.1.8.6 Symbol onig_end@@ (64-bit UNIX System V ABI AMD x86-64 architecture) present 3 times /usr/lib64/php5/bin/php-cgi /usr/lib64/php5/bin/php /usr/lib64/libruby18.so.1.8.6 It would be nice if they could use a system copy of it rather than duplicating...
You can try your luck at http://bugs.php.net/ ;) Other than that, breaking mbstring is not really a viable option here and making php depend on ruby for this plain sucks. Anyway, a separate bug from ruby please.
Considering that onigurama is not in portage now, and that _both_ languages use it, I can't see how am I asking to break something or get php to depend on ruby. The best thing here is _coordinating_ between the two teams, as they both need onigurama.
PHP moved to Bug 206970.
(In reply to comment #2) > Considering that onigurama is not in portage now Sure it is (dev-libs/oniguruma), you've got a typo there... :) Plus the whole mixing of two completely unrelated ebuilds got me confused like hell. And please note that previous attempts to use shared libraries for PHP mostly broke the thing (like when trying to use shared dev-libs/libpcre).
doh! and I even double checked. Sorry =_=; seems like my head's spinning because of all the symbol mangling.
Won't happen for dev-lang/ruby since we need a special version for 1.8.6 and we need it to help patch the ruby 1.8.6 source code before compiling. Not a simple library dependency. On the bright side ruby 1.9 will have support for a newer oniguruma built in, so I guess that will make things easier.