Summary: | =app-misc/lirc-0.9.0-r2: fails to build on ppc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anthony Basile <blueness> |
Component: | Current packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Anthony Basile
2012-09-08 17:42:49 UTC
Regarding the issues with the headers and building against the kernel sources -- the reason lirc does this is because it builds a LOT of kernel modules. That said, I will look into this to figure out why it's using the wrong path, as I believe the path would be controlled by the linux-mod eclass rather than the lirc build system but I need to confirm this. I was right, this is all handled in linux-mod.eclass , along with toolchain-funcs.eclass. According to that eclass, it is already as of 2.6.16 and above returning 'powerpc' instead of 'ppc' or 'ppc64'. I also checked by hand and it seems tc-arch-kernel's kernel-version check does handle 3.x versions properly. On my system, ARCH="amd64" is properly replaced with 'x86' in said path, so as far as I can tell the path is being properly mangled. It might be worth noting that tc-arch-kernel uses CTARGET (or CHOST if unset) plus the kernel version to determine the appropriate ARCH , so it's possible that if your CTARGET:-CHOST doesn't match 'powerpc*' this would probably be why it's failing.. Without the full build.log and emerge --info output i won't be able to do any further analysis. Found the bug. It's not a lirc ebuild issue. *** This bug has been marked as a duplicate of bug 432390 *** |