[BusyBox] Problem executing external commands in BusyBox/ash (0.60.5)
Michael Boman
michael.boman at securecirt.com
Fri Nov 8 07:40:03 UTC 2002
On Fri, Nov 08, 2002 at 02:05:20PM +0100, Ole-Egil Hvitmyren wrote:
> Michael Boman wrote:
> > On Fri, Nov 08, 2002 at 10:24:51AM +0100, Magnus Damm wrote:
> >
> >>Stupid question:
> >>
> >>Did you compile the non-busybox commands yourself?
> >
> >
> > Yes
> >
> >
> >>If not - do you have the correct libraries installed?
> >
> >
> > I belive all the libraries I need are installed, but I can't check as I
> > can't execute external commands (so I can't run 'ldd' and check).
> >
> > I compile the stuff (uClibc, BusyBox, e2fsprogs, util-linux) like this
> > (cut&paste from my build.sh script):
> >
>
> But you seem to compile the external commands against normal libc on the
> host, then procede to install them on the target. On the target you're
> running uClibc. Right?
You are so right. The tools was compiled against glibc and not
uClibc.. But I thougt the uClibc gcc compiler would take care of that? How
can I compile the tools against uClibc? (see my earlier compile script
for my current [non-working] compile options).
Best regards
Michael Boman
More information about the busybox
mailing list