Summary: | sys-apps/busybox-1.00-r4 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sophie Hamilton <gentoo-bugs> |
Component: | [OLD] Core system | Assignee: | Embedded Gentoo Team <embedded> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sophie Hamilton
2005-06-15 18:28:36 UTC
unset KBUILD_OUTPUT and see if it helps Unsetting KBUILD_OUTPUT yields the same output as before, as does copying the kernel .config file manually to /usr/src/linux/.config: ===== downstairs ciaran # echo $KBUILD_OUTPUT /var/tmp/kernel-output/2.6.9 downstairs ciaran # unset KBUILD_OUTPUT downstairs ciaran # echo $KBUILD_OUTPUT downstairs ciaran # emerge -u busybox [...emerge fails with same errors as before...] make: *** No rule to make target `busybox'. Stop. !!! ERROR: sys-apps/busybox-1.00-r4 failed. !!! Function src_compile, Line 142, Exitcode 2 !!! build failed !!! If you need support, post the topmost build error, NOT this status message. downstairs ciaran # cp /var/tmp/kernel-output/2.6.9/.config /usr/src/linux/. downstairs ciaran # emerge -u busybox [...again, emerge fails...] make: *** No rule to make target `busybox'. Stop. !!! ERROR: sys-apps/busybox-1.00-r4 failed. !!! Function src_compile, Line 142, Exitcode 2 !!! build failed !!! If you need support, post the topmost build error, NOT this status message. ===== made sure KBUILD_OUTPUT is unset in src_unpack too ... I'll be trying that tomorrow, but even if it does work it won't have been fixed, it'll be a klugy workaround, involving a manual ebuild edit. Based on this reasoning, I'm reopening the bug, although I haven't tried your workaround yet, so I'll let you know how I get on tomorrow. One thing; I'm fairly certain that the .config file referred to is NOT the kernel .config file. BusyBox itself uses its own .config file, with the same sort of syntax as the kernel config file. As far as I know, BusyBox doesn't have any sort of communication with the kernel files, so KBUILD_OUTPUT shouldn't be affecting anything. Again, though, I'll have more information on this tomorrow when I have time to try it. what are you talking about ? i changed the busybox ebuild in cvs, i wasnt telling you to do it yourself |