On Tuesday, 27. October 2009 19:14:33 Denys Vlasenko wrote: > On Tue, Oct 27, 2009 at 5:43 PM, Reinhard Thies <[email protected]> wrote: > > On Tuesday, 27. October 2009 16:04:50 Denys Vlasenko wrote: > >> On Tue, Oct 27, 2009 at 3:23 PM, Reinhard Thies <[email protected]> > > > > wrote: > >> > Hi, > >> > > >> > I am trying to cross-compile busybox using ELDK 4.2. > >> > When I try make I get the following error: > >> > ppc_6xx-gcc -Wall -Wshadow -Wwrite-strings -Wundef > >> > -Wstrict-prototypes -Wunused -Wunused-parameter -Wunused-function > >> > -Wunused-value > >> > -Wmissing-prototypes -Wmissing-declarations > >> > -Wdeclaration-after-statement -Wold-style-definition > >> > -fno-builtin-strlen -finline-limit=0 > >> > -fomit-frame-pointer -ffunction-sections -fdata-sections > >> > -fno-guess-branch-probability -funsigned-char -static-libgcc > >> > -falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1 > >> > -Os -std=gnu99 -Iinclude -Ilibbb -include include/autoconf.h > >> > -D_GNU_SOURCE -DNDEBUG -D"BB_VER=KBUILD_STR(1.16.0.git)" > >> > -DBB_BT=AUTOCONF_TIMESTAMP applets/usage_pod.c m crypt -o > >> > applets/usage_pod > >> > ppc_6xx-gcc: m: No such file or directory > >> > ppc_6xx-gcc: crypt: No such file or directory > >> > > >> > Any ideas ? > >> > >> You have some environment variable (LDLIBS or some such) > >> which gets inserted into compile command and breaks it. > >> > >> Try "env - PATH=$PATH make". If it works, then this is it. > >> -- > >> vda > > > > Denys, > > > > thanks its compiling now. > > You just ran "env - PATH=$PATH make" without trying to figure out > what's wrong, right? > > You need to find out how your environment ended up polluted, > not just blindly use a workaround. > > But stops at link time now with the following : > > Trying libraries: crypt m > > Library crypt is not needed, excluding it > > Library m is needed, can't exclude it (yet) > > Final link with: m > > > > So how can I add the libs ? > > Did you notice that this isn't an _error_ message? > -- > vda Denys,
> You just ran "env - PATH=$PATH make" without trying to figure out > what's wrong, right? > > You need to find out how your environment ended up polluted, > not just blindly use a workaround. > You doing me wrong. The only thing you are rigth with is that I am nearly blind. I tried to figure out but was not able to find . > Did you notice that this isn't an _error_ message? Sorry, no I didn't. If I did I hadn't asked. So what is it telling me ? Thx, Reinhard _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
