make[3]: Nothing to be done for `install-exec-am'. if test -n 'btctl.dll'; then \ /usr/lib/pkgconfig/../../bin/gacutil /i btctl.dll /f /package libbtctl /root /var/tmp/portage/net-wireless/libbtctl-0.10.0/image//usr/lib || exit 1; \ fi Failure adding assembly btctl.dll to the cache: Strong name cannot be verified for delay-signed assembly make[3]: *** [install-data-local] Error 1 make[3]: Leaving directory `/var/tmp/portage/net-wireless/libbtctl-0.10.0/work/libbtctl-0.10.0/mono/libbtctl' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/var/tmp/portage/net-wireless/libbtctl-0.10.0/work/libbtctl-0.10.0/mono/libbtctl' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/net-wireless/libbtctl-0.10.0/work/libbtctl-0.10.0/mono' make: *** [install-recursive] Error 1 Reproducible: Always
This bug is also present with =net-wireless/libbtctl-0.9.0
I'll try recompiling all it's $DEPEND's later today.
The same here.
Looks like it's calling /usr/bin/gacutil which belongs to mono # qfile /usr/bin/gacutil =dev-lang/mono-2.0.1
Confirming, libbtctl-0.10.0 building is broken with mono use flag
Confirmed also. The following hacks around this issue: # echo "net-wireless/libbtctl -mono" >> /etc/portage/package.use However, alsoa, with use flag mono, would this stop gnome-2.24* from going stable? Other then this package, I believe I had zero problems marking gnome-2.24* stable here. (Aside from issues with gtk-sharp after also marking mono-2* stable here.)
@dotnet, is it something similar to gmime ?
I'll take a look. It's probably the same problem. It needs a key (constant across rebuilds) to sign it to get into the gac of newer monos.
Yep, it's broken. Since nothing in tree uses the mono bindings, I have just punted the useflag with Gilles' blessing.