Alias-ing problem

[Denys Vlasenko]

On Thursday 12 March 2009 04:30:41 pm Sergio wrote:
> Hi list,
> 
> I'm using two different (version) cross-compilers for a PPC board. One of
> them compiles a BB with a problem in the alias builtin command.
> 
> The BB sources and configuration are absolutely the same on both PC.
> 
> These are two outputs, the first from the working one:
> 
> *** working ***
> PMFU_1:~/bb # alias
> la='ls -la'
> PMFU_1:~/bb #
> PMFU_1:~/bb # la
> drwxr-xr-x    2 root     root            0 Jan  1 01:42 .
> drwxr-xr-x    3 root     root            0 Jan  1 01:42 ..
> -rwxr-xr-x    1 root     root       309912 Jan  1 01:27 busybox-ko
> -rwxr-xr-x    1 root     root       313084 Jan  1 01:34 busybox-ok
> PMFU_1:~/bb #
> PMFU_1:~/bb # la /bin/busybox
> -rwxr-xr-x    1 root     root       313084 Jan  1 01:57 /bin/busybox
> PMFU_1:~/bb #
> 
> **** not working ****
> PMFU_1:~/bb # alias
> la='ls -la'
> PMFU_1:~/bb #
> PMFU_1:~/bb # la
> ls: invalid option -- .
> BusyBox v1.13.3 (2009-03-12 14:43:18 CET) multi-call binary
> 
> Usage: ls [-1AacCdeilnRrSsTtuvwxXk] [filenames...]
> 
> PMFU_1:~/bb # ls -la
> drwxr-xr-x    2 root     root            0 Jan  1 01:42 .
> drwxr-xr-x    3 root     root            0 Jan  1 01:42 ..
> -rwxr-xr-x    1 root     root       309912 Jan  1 01:27 busybox-ko
> -rwxr-xr-x    1 root     root       313084 Jan  1 01:34 busybox-ok

Woohoo.

run "make shell/ash.s" with both compilers and try to see what's different
in ash.s. Post the ash.s files to the list.
--
vda