Here is another post on the cross-compile series for DroboFS.
Introduction: Why nano?
I like it better than vi. Oh yeah, I said it.
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
Step 4: Get the source code
nano’s website: http://www.nano-editor.org/
Direct link: http://www.nano-editor.org/dist/v2.2/nano-2.2.5.tar.gz
Make sure that you are in the folder /root/code, then type:
tar zxf nano-2.2.5.tar.gz
Step 5: Configuration
Before configuring, a little change has to be made in the include folders:
ln -s /usr/arm/include/ncurses/ncurses.h /usr/arm/include/
If you do not create this soft link, the compilation will fail because it will not find the ncurses.h file.
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/nano-2.2.5:
Again, there should be no errors. If any errors are reported, make sure you performed steps 3, 4 and 5 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.
Now you can run nano on your DroboFS. Enjoy the freedom from vi!