Prebuild binaries: more detailed setup info/parameters (busybox/aboriginal) ?

[piquemal michel]

Dear Rob,

Ok I did take a fresh restart on this.

Pulled:
http://landley.net/aboriginal/downloads/old/binaries/1.2.0/cross-compiler-mipsel.tar.bz2

http://landley.net/aboriginal/downloads/old/binaries/1.2.0/system-image-mipsel.tar.bz2

and
http://www.busybox.net/downloads/busybox-1.20.0.tar.bz2


I'd like to be able then to produce the same busybox-mipsel than:
http://www.busybox.net/downloads/binaries/1.20.0/busybox-mipsel (file size 1565444)

which works on my HW target

So I did setup disccd on host and launched aboriginal system image with ./dev-environemet.sh
(distcc acceleration reported as enabled).
Went to busybox-1.20.0 directory and did
make defconfig
LDFLAGS="--static" make

It did generate a static busybox (stripped, file size 1568008, so different from pre-built one!), working inside aboriginal system image... and target!
I'm unsure about the issue(s) I had earlier, as I tried so many combinations...To be honest, maybe my transfer method to the target might have altered the files too...

Still, compiled binary differs a bit from prebuilt binary, but hey, it works now, so I won't complain! There might be some other LDFLAG or something involved for pre-built binaries.

There's only an issue if I rename busibox executable file, but it seems an already discussed issue/feature, and I can live with that.

Thanks a lot Rob for your timely help and support.
Keep-up the great work on aboriginal: it's really extremely useful!

Best,