[BusyBox] module/s don't build
Mark Richards
mark.richards at massmicro.com
Wed Dec 15 18:09:34 UTC 2004
In an embedded system that uses BusyBox (much to its credit) I have updated to
version 1.00.rc2 and recently 1.0 release. I managed to get the rc2 to work
(using a GNU CRIS crocc-compiler), however when I last left this project I
still was having trouble adding "dc" to the build.
It's still happening :)
I just want to ask any experienced BusyBox folks if I'm correct to run make
menuconfig, select the module I want to include, save the .config file, then
run make dep and finally make?
There's a note in the README about doing a make dep after the config, however
this sometimes yields the message "nothing to be done for dep", so I assume
that it's fine. However, there was an occasion where make dep did some stuff
(sorry I'm new at this), but even following the make, my module ("dc") was
still missing (invoked with "busybox dc"). So I guess make dep isn't at
fault. It's probably me :) Any ideas?
As a positive note, I've used a lot of tools with the cross compiler and this
has to be the simplest and easiest to use in my environment. I didn't have
to change a thing in the Makefile, although the system I use mandates an
include that brings in the rules file for a build. I added in the recommended
statement anywat, but this also did not help my situation.
More information about the busybox
mailing list