on a x86_64-w64-mingw32 cross emerge (cross environment created with crosstool-ng), protobuf fails to emerge. Compilation is fine, but it fails in the install phase, the relevant part of the build log is: * No matching library found with SLOT variable, currently set: 0/32 * Expected value: /usr/x86_64-w64-mingw32/tmp/portage/dev-libs/protobuf-21.9/image/usr/lib/libprotobuf.so.32 * ERROR: dev-libs/protobuf-21.9::gentoo failed (install phase): * Please update SLOT variable i've taken a look at the ebuild, and found this: if [[ ! -f "${ED}/usr/$(get_libdir)/libprotobuf.so.${SLOT#*/}" ]]; then eerror "No matching library found with SLOT variable, currently set: ${SLOT}\n" \ "Expected value: ${ED}/usr/$(get_libdir)/libprotobuf.so.${SLOT#*/}" die "Please update SLOT variable" fi this expects the created libraries to have a filename pattern, that they don't have. the filename created with this cross build is libprotobuf.dll.a. Either this if block should be only executed on Linux, or similar platforms. I guess it should be possible to check this. On the other hand, this block looks like a help for the package maintainer "only". Only in ", because I don't want to belittle maintainer's work, I'm just wondering if this is the right place for this. full log/emerge --info in attachement Reproducible: Always
Created attachment 848879 [details] emerge-x86_64-w64-mingw32 --info
Created attachment 848881 [details] build.log
I suppose could put in src_test.
(In reply to Sam James from comment #3) > I suppose could put in src_test. this would break, if someone wants to also use FEATURES="test" (or is this a different test?), which I currently don't want to do. So for me, it would be fine...