The problem is also reproductible with monodoc-1.2.4 Reproducible: Always Steps to Reproduce: 1.emerge monodoc (or monodevelop wich pulls monodoc) Actual Results: monodoc can't be installed. >>> Install monodoc-1.9 into /var/tmp/portage/dev-util/monodoc-1.9/image/ category dev-util make -j3 -j1 DESTDIR=/var/tmp/portage/dev-util/monodoc-1.9/image/ install Making install in engine make[1]: Entering directory `/var/tmp/portage/dev-util/monodoc-1.9/work/monodoc-1.9/engine' make[2]: Entering directory `/var/tmp/portage/dev-util/monodoc-1.9/work/monodoc-1.9/engine' make[2]: Nothing to be done for `install-exec-am'. /usr/bin/gacutil /i monodoc.dll /f /package monodoc /gacdir /usr/lib /root /var/tmp/portage/dev-util/monodoc-1.9/image//usr/lib Failure adding assembly monodoc.dll to the cache: Strong name cannot be verified for delay-signed assembly make[2]: *** [install-data-local] Error 1 make[2]: Leaving directory `/var/tmp/portage/dev-util/monodoc-1.9/work/monodoc-1.9/engine' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/var/tmp/portage/dev-util/monodoc-1.9/work/monodoc-1.9/engine' make: *** [install-recursive] Error 1 * * ERROR: dev-util/monodoc-1.9 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 2495: Called die * The specific snippet of code: * emake DESTDIR="${D}" install || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-util/monodoc-1.9/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/monodoc-1.9/temp/environment'. * Expected Results: monodoc being installed.
By bad... I was installing monodoc-1.9 and have mono-2.0.1 installed... sry guys. Keep the good work.
