| Summary: | busybox uses KBUILD_OUTPUT in an incorrect way | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Richard Westwell <garlicbread> |
| Component: | [OLD] Core system | Assignee: | Embedded Gentoo Team <embedded> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gentoo-bugs |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=932445 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
the ebuild now unsets the variable, thanks but src_compile() needs to unset KBUILD_OUTPUT too. if not it is trying to brake
sandbox with open_wr ${KBUILD_OUTPUT}/Rules.mak
busybox-1.00-r4
It seems busybox_set_env should be called in src_unpack as well. Otherwise busybox attempts to create Rules.mak in the wrong directory when KBUILD_OUTPUT is set |
if KBUILD_OUTPUT has been set prior to emerging busybox e.g. if your trying to relocate the kernel build directory to within /var/tmp/kernel-output via config-kernel busybox will output it's .config file to the directory specified by KBUILD_OUTPUT instead of the temporary build directory ${S} this happens during "make allyesconfig > /dev/null" this overwrites the kernel .config file already present and causes the build to not generate /bin/busybox during the install phase the way around it is just to put unset KBUILD_OUTPUT in src_unpack at the beginning Reproducible: Always Steps to Reproduce: 1. set KBUILD_OUTPUT e.g. KBUILD_OUTPUT="/var/tmp/kernel-output/2.6.11-mygen-r2/" in /etc/env.d/05kernel 2. env-update to set the variable 3. emerge busybox Actual Results: /var/tmp/kernel-output/<kern version>/.config overwritten lack of /bin/busybox in the installation