Summary: | dev-util/mingw64-runtime fails to build. With Invalid configuration. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cihan Özakça <cozakca> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cihan Özakça
2020-09-28 11:26:08 UTC
Build.log * Package: dev-util/mingw64-runtime-7.0.0-r1 * Repository: gentoo * Maintainer: toolchain@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc idl kernel_linux libraries tools userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * ERROR: dev-util/mingw64-runtime-7.0.0-r1::gentoo failed (setup phase): * Invalid configuration * * Call stack: * ebuild.sh, line 125: Called pkg_setup * mingw64-runtime-7.0.0-r1.ebuild, line 54: Called die * The specific snippet of code: * die "Invalid configuration" * * If you need support, post the output of `emerge --info '=dev-util/mingw64-runtime-7.0.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-util/mingw64-runtime-7.0.0-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-util/mingw64-runtime-7.0.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/mingw64-runtime-7.0.0-r1/temp/die.env'. * Working directory: '/var/tmp/portage/dev-util/mingw64-runtime-7.0.0-r1/homedir' * S: '/var/tmp/portage/dev-util/mingw64-runtime-7.0.0-r1/work/mingw-w64-v7.0.0' Seems you tried to emerge it as-is, it's masked for a reason. See wiki for crossdev-based instructions: https://wiki.gentoo.org/wiki/Mingw The package is used only in context of creatin cross-toolchains, like: # crossdev --target x86_64-w64-mingw32 # crossdev --target i686-w64-mingw32 https://wiki.gentoo.org/wiki/Mingw has a few hints. |