Summary: | nvidia-kernel build fails because wrong ARCH gets passed to kernel | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Gluck <jgluckca> |
Component: | New packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | jackmort37, johnm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The attachment is the log for a failed build |
Description
John Gluck
2004-12-01 16:11:49 UTC
Created attachment 45099 [details]
The attachment is the log for a failed build
Same problem here on amd64... Needs to use set_arch_to_kernel() and set_arch_to_portage() from eutils.eclass. Johnm : see the above comment, should this be done in the linux-info eclass? Actually for a point of reference, this doesnt happen here. Which is very weird. doesnt happen here either. its actually caused simply by ARCH being set. Will look at it shortly. The ebuilds used to unset ARCH before compiling... That could just go back into them if necessary. Could you please emerge sync, and then try again. please re-open if you still have problems, and let me know how you get on with a comment. cheers. I sucessfully emerged nvidia-kernel-1.0.6629 on December 5th without having to make a softlink. I guess the problem is fixed. John Excellent, glad its all working OK. Yep, I can confirm it also works for me. |