Here is another post on the cross-compile series for DroboFS.
Introduction: Why bash?
It is my favorite shell environment. YMMV.
Overall compiling complexity: Easy.
Step 1: Background info
To be able to make use of this post, you need a VM configured as indicated in this post.
Step 2: Enter the cross-compiling environment
See step 2 of this post to see instructions on how to enter the chroot environment.
Step 3: Dependencies
As far as I can remember, bash has no dependencies.
Step 4: Get the source code
Make sure that you are in the folder /root/code, then type:
tar zxf bash-4.1.tar.gz
Step 5: Configuration
The traditional configure command applies:
./configure --host=arm-none-linux-gnueabi --prefix=/usr/arm
This should return no errors. If it does, you have to check if you have all required packages in your chroot (although, if you have been following the dependencies, you should have all of them).
Step 6: Compiling
Within the folder /root/code/bash-4.1:
Again, there should be no errors. If any errors are reported, make sure you performed steps 3 and 4 correctly. If you still have errors, make sure that the VM is properly configured (e.g. like I did the first time around, when I got the wrong toolchain, or forgot to ‘export’ the proper compiler flags).
Step 6: Installing
As simple as it gets:
…which will place the compiled library under /usr/arm.
Then we package the whole /usr/arm and copy it over to the DroboFS, as indicated on step 9 here.
As an additional step, I would copy /usr/arm/bin/bash to /bin/bash on the DroboFS, so that if you ever lose your disk pack you’d still be able to log in through SSH.
Changing the default shell for the root account is left as an exercise to the reader, since there is a lot of feedback from DR employees not to do that unless you really, really know what you are doing.
Now you can run bash on your DroboFS.