Bug 499 - make O=... busybox-menuconfig crashes
Summary: make O=... busybox-menuconfig crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-29 15:00 UTC by Thomas Petazzoni
Modified: 2009-09-14 18:37 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Petazzoni 2009-07-29 15:00:39 UTC
make busybox-menuconfig crashes when used with the out-of-tree option O=:

#
# using defaults found in .config
#

interrupted(11)
make[3]: *** [menuconfig] Error 1
make[2]: *** [menuconfig] Error 2
make[2]: Leaving directory `/home/thomas/local/buildroot-basic/project_build_arm/uclibc/busybox-1.14.2'
make[1]: *** [busybox-menuconfig] Error 2
make[1]: Leaving directory `/home/thomas/local/buildroot'

Interestingly, manually doing

make __TARGET_ARCH=arm -C /path/to/the/build/directory/project_build_arm/uclibc/busybox-1.14.2 menuconfig

works nicely. So it's the fact that it's been run by the Buildroot infrastructure that makes it crash.
Comment 1 Peter Korsgaard 2009-07-29 18:39:20 UTC
Strange - It works here (both with a clean tree and after a full build).
The only issue I remember about O= was fixed long ago with 94b3420da9c94c3044f, where packages that also support O= (linux, busybox, ..) got confused as it got forwarded.
Comment 2 Peter Korsgaard 2009-08-31 07:51:25 UTC
(In reply to comment #1)
> Strange - It works here (both with a clean tree and after a full build).
> The only issue I remember about O= was fixed long ago with 94b3420da9c94c3044f,
> where packages that also support O= (linux, busybox, ..) got confused as it got
> forwarded.

Thomas, are you still seeing this issue? 

Comment 3 Thomas Petazzoni 2009-09-14 18:37:52 UTC
For some reason, works now with Busybox 1.15.0. Either I was crazy when I encountered the issue, or something fixed it. Who knows.