# emerge =app-office/openerp-server-5.0.6 -q [...] >>> Emerging (20 of 20) app-office/openerp-server-5.0.6 >>> Failed to emerge app-office/openerp-server-5.0.6, Log file: >>> '/mnt/auto/vartmp/portage/app-office/openerp-server-5.0.6/temp/build.log' * Package: app-office/openerp-server-5.0.6 * Repository: gentoo * Maintainer: elvanor@gentoo.org * USE: amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox python2.6 setup.py build Error: python module libxml2 (libxml2 python bindings) is required Error: python module libxslt (libxslt python bindings) is required * ERROR: app-office/openerp-server-5.0.6 failed: * Building failed After add USE='python' and remerge "dev-libs/libxslt" && "dev-libs/libxml2" the ebuild works fine. # USE='python' emerge dev-libs/libxslt dev-libs/libxml2 -q1 && emerge =app-office/openerp-server-5.0.6 -q >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-office/openerp-server-5.0.6 >>> Installing (1 of 1) app-office/openerp-server-5.0.6 >>> Recording app-office/openerp-server in "world" favorites file... * Messages for package app-office/openerp-server-5.0.6: * In order to setup the initial database, run: * emerge --config =app-office/openerp-server-5.0.6 * Be sure the database is started before * GNU info directory index is up-to-date. !!! existing preserved libs found Both packages are dependency of dev-python/lxml. I do not know enough about, but I think maybe needs dev-python/lxml this two libs with USE='python'? Maybe a dev-libs/libxslt[python] dev-libs/libxml2[python] in the "{RD,D}EPEND" section will help, but I do not know if was better to blame "dev-python/lxml" or "app-office/openerp-server".
Hmm, I don't know either if it would be better to add this to lxml or openerp. Python herd, can you advise?
app-office/openerp-server directly uses libxml2 and libxslt Python modules, so app-office/openerp-server should additionally depend on: dev-libs/libxml2[python] dev-libs/libxslt[python] dev-python/lxml does NOT import libxml2 and libxslt Python modules. Extension modules of dev-python/lxml are linked against some libraries of dev-libs/libxml2 and dev-libs/libxslt, which are installed even with USE="-python". $ scanelf -qF '%F: %n' `qlist dev-python/lxml | sort` /usr/lib64/python2.6/site-packages/lxml/etree.so: libxslt.so.1,libexslt.so.0,libxml2.so.2,libpython2.6.so.1.0,libpthread.so.0,libc.so.6 /usr/lib64/python2.6/site-packages/lxml/objectify.so: libxml2.so.2,libpython2.6.so.1.0,libpthread.so.0,libc.so.6 /usr/lib64/python2.7/site-packages/lxml/etree.so: libxslt.so.1,libexslt.so.0,libxml2.so.2,libpython2.7.so.1.0,libpthread.so.0,libc.so.6 /usr/lib64/python2.7/site-packages/lxml/objectify.so: libxml2.so.2,libpython2.7.so.1.0,libpthread.so.0,libc.so.6 /usr/lib64/python3.1/site-packages/lxml/etree.so: libxslt.so.1,libexslt.so.0,libxml2.so.2,libpython3.1.so.1.0,libpthread.so.0,libc.so.6 /usr/lib64/python3.1/site-packages/lxml/objectify.so: libxml2.so.2,libpython3.1.so.1.0,libpthread.so.0,libc.so.6
Fixed, thanks for the report
