| Summary: | sys-boot/gnu-efi installs in /usr/lib instead of /usr/$(get_libdir) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Hristo Venev <hristo> |
| Component: | [OLD] Core system | Assignee: | IA-64 team <ia64> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Oh and EPREFIX
--- sys-boot/gnu-efi/gnu-efi-3.0u.ebuild
+++ sys-boot/gnu-efi/gnu-efi-3.0u.ebuild
@@ -32,7 +32,7 @@
}
_emake() {
- emake prefix=${CHOST}- ARCH=${iarch} PREFIX=/usr "$@"
+ emake prefix=${CHOST}- ARCH=${iarch} PREFIX="${EPREFIX}/usr" LIBDIR="${EPREFIX}/usr/$(get_libdir)" "$@"
}
src_compile() {
What files get put there? Does it make sense for any scenario to have them both, 32bit and 64bit when ia64 is 64bit-only arch? I expect not to. Provide more details/reasoning about why you think multilib should be used here. |
--- sys-boot/gnu-efi/gnu-efi-3.0u.ebuild +++ sys-boot/gnu-efi/gnu-efi-3.0u.ebuild @@ -32,7 +32,7 @@ } _emake() { - emake prefix=${CHOST}- ARCH=${iarch} PREFIX=/usr "$@" + emake prefix=${CHOST}- ARCH=${iarch} PREFIX=/usr LIBDIR=/usr/$(get_libdir) "$@" } src_compile() { Reproducible: Always