Bekijk de volledige versie : did anyone succeded to replace Busybox with newest version?
I guess it is not so easy because Busybox uses uClibc and not glibc. ASUS has a strange setting in .config CROSS_COMPILER_PREFIX="bogus-config-error-"
It seems that it is not possible to run ipkg.sh on BusyBox v1.00-pre2
Or I am mistaken and should enable something more in busybox configuration?
Could anybody cexplain me this situation?
Gregoire.Favre
18-11-2006, 07:18
I didn't test it, but couldn't the one for openwrt work ?
It's very easy to compil openwrt trunk's tree for bcrm 2.6 and then you have all binaries you could dream of.
My busybox_1.2.1-1_mipsel.ipk is only 309kb if you want it :)
And I put quiete a lots in it (etherwake,...)
fireflash
18-11-2006, 17:10
It seems that it is not possible to run ipkg.sh on BusyBox v1.00-pre2
HUH? I got it to run just fine on the stock version of busybox. Just had to modify the script file and the config file to work around the router's messed up filesystem.
HUH? I got it to run just fine on the stock version of busybox. Just had to modify the script file and the config file to work around the router's messed up filesystem.
I'm getting error:
# ./ipkg.sh
sed: invalid option -- r
BusyBox v1.00-pre2 (2006.11.16-18:49+0000) multi-call binary
Usage: sed [-nef] pattern [files...]
That sounds like the ipkg shell script is trying to use a parameter -r to sed (the stream editor) whereas the local version of sed that you have doesn't support that option. The -r parameter specifies extended regular expressions, not sure if you will be able to get away without it or not... the -e just does plain expressions, so that may get you through ok.