Bug 5858

Summary: attempting to repoint the Bash command to busy box fails on bash scripts
Product: Busybox Reporter: hardcorefs <hardcore>
Component: OtherAssignee: unassigned
Status: RESOLVED WONTFIX    
Severity: major CC: busybox-cvs
Priority: P5    
Version: 1.19.x   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Host: Target:
Build:

Description hardcorefs 2013-01-07 06:27:44 UTC 
Repointed "Bash" command to busybox
 but when using it to compile a make filescript for the following it fails:

wget http://www.orbit-lab.org/kernel/compat-wireless/2012/12/compat-wireless-2012-12-17.tar.bz2
tar xvf compat-wireless-2012-12-17.tar.bz2
cd comp*


./scripts/driver-select ath9k_htc
./scripts/driver-select: line 46: function: not found
Usage: ./scripts/driver-select [ <driver-name> | <driver-group-name> | restore ]
Supported 802.11 drivers:
        ath5k
        ath9k
        ath9k_ap
        ath9k_htc
        carl9170
        ath6kl
        b43
        zd1211rw
        rt2x00
        wl1251
        wl12xx
        brcmsmac
        brcmfmac

Supported Ethernet drivers:
        atl1
        atl2
        atl1e
        atl1c
        alx
Supported DRM drivers:
        i915

Supported group drivers:
        atheros <  ath5k ath9k carl9170 zd1211rw ath6kl>
        ath <  ath5k ath9k carl9170 ath6kl>
        brcm80211 <  brcmsmac brcmfmac >
        intel <  iwlwifi, iwlegacy >
        rtl818x <  rtl8180 rtl8187 >
        rtlwifi <  rtl8192ce >
        ti <  wl1251 wl12xx (SPI and SDIO)>

Supported group drivers: Bluetooth & Ethernet:
        atlxx <  atl1 atl2 atl1e alx>
        bt <  Linux bluetooth drivers >

Supported group drivers: DRM:
        drm <  i915>
Restoring compat-drivers:
        restore: you can use this option to restore compat-drivers to the original state
./scripts/driver-select: line 85: syntax error: unexpected "}"
#
Comment 1 Mike Frysinger 2013-01-08 02:59:37 UTC 
some shells provide limited bash compatibility (assuming you enabled it -- but you didn't post your .config, so it's hard to say), but it is *not* a goal to re-implement all of bash.

if you have code targeting bash, then use bash.

in this case, it looks like the old function syntax isn't working:
  function usage {