root@Omega-0BED:/# opkg install gcc
Installing gcc (4.8.3-1) to root...
Collected errors:

• verify_pkg_installable: Only have 8884kb available on filesystem /overlay, pkg gcc needs 20983
• opkg_install_cmd: Cannot install package gcc.

I noticed that the partition /tmp has 30Mb and / has 8Mb. I was wondering if there was a way of resizing / to have more space.

Thanks

Ajay

/tmp is a RAM disk, which means after your do a reboot, it will disappear. You might want to check out the tutorial here that shows you how to mount a USB drive to the Omega: https://onion.freshdesk.com/support/solutions/articles/6000080075-how-can-i-use-usb-storage- Moreover, it's not recommended to install gcc on the Omega. If you want to compile programs for the Omega, it's generally recommended to setup a cross-compile environment on your computer/server to compile for it.

For more information about setting up the cross-compile environment, please take a look at this guide: https://github.com/OnionIoT/OpenWRT-Packages/wiki/Setting-Up-the-Cross-Compile-Environment

Cheers!

I read through the link you provided about the cross-compile environment. It looks like you have to download and compile the entire OpenWRT OS just to get the cross-compile environment.

I'm not interested in tinkering with the OS or creating packages at this point - I just want to compile some small executables. Isn't there a cross-compile toolchain somewhere that would just allow me to compile executables?

Bryan

I too have been struggling with the full OpenWRT OS build as given in the instructions and would really like just a basic set of C/C+ tool chain for cross compilation without the full OS stuff

I accessed the compilers etc. from
/home/kit/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_musl-1.1.11/

Using this,I appeared to be able to successfully build a small, very simple test program (testc) which I then copied to my Omega but when I try to run it on my Omega, all I get is:

root@Omega:~# ls -l
-rwxrwxrwx    1 root     root          8994 Nov 18 12:26 testc
root@Omega:~# ./testc
-ash: ./testc: not found
root@Omega:~#

So clearly I have done something wrong, but I haven't a clue what:-)
Anyone have any thoughts?

Also, we have a few ideas to make compiling for the Omega a bit easier, such as setting up a shared compilation server where you can upload files to be compiled and it generates an opkg file for you to download. We welcome any idea on how we can scale this thing so that the server won't blow up if 100 people requested to compile something simultaneously.

That's also why we are working so hard on the wrapper functions for various scripting languages! This will allow you to write software and get it to run on the Omega without compiling anything

• I will certainly look at the reference you give in your first reply above: we have the toolchain in their binary format for some architectures available for download at https://onion.io/downloads.
• Regarding your comment: which means you can compile the code into binary, but the system wouldn't know to install it into /bin so that you can execute it in the terminal
  I am puzzled here. Why would I need to put an executable file in /bin just to run it. I would have thought that any correctly compiled executable file would be capable of running from anywhere.
  I have tried putting the executable into all of the following directories just in case I was misunderstanding something: /bin, /sbin, /usr/bin, /usr/sbin and get the same not found message in all cases.
  I have also tried copying the fast-gpio file I built using https://github.com/OnionIoT/OpenWRT-Packages/wiki/Setting-Up-the-Cross-Compile-Environment and that gives the same not found message no matter what I do.
  I can successfully run an executable shell script, so I guess I am doing something wrong somewhere with my build processes.
  I will keep digging and see what I can find:-(

Which operating system are you using currently?

I'm using Ubuntu (Kubuntu) 15.10 64-bit (AMD64). My OS is running under VMWare, so there's a fair chance I could match whatever environment you told me to. I will note that compiling OpenWRT using your instructions (Setting Up the Cross Compile Environment) took well over an hour in VMWare!

I'm puzzled like Kit Bishop why OpenWRT won't just run an executable, but I'm used to cross-compiling to uClinux so there must be some differences. I'm going to start playing around with adding a small package to see if I can get something to run on the Omega.

SDK: https://onion-cdn.s3.amazonaws.com/community/openwrt/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar
Toolchain: https://onion-cdn.s3.amazonaws.com/community/openwrt/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar

The links should become active in a little bit.

EDIT: I posted the wrong links...

SDK: https://s3-us-west-2.amazonaws.com/onion-cdn/community/openwrt/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar.bz2
Toolchain: https://s3-us-west-2.amazonaws.com/onion-cdn/community/openwrt/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar.bz2

• For: SDK: https://onion-cdn.s3.amazonaws.com/community/openwrt/OpenWrt-SDK-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar I get:
  This XML file does not appear to have any style information associated with it. The document tree is shown below.
  <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>37A96A62308BF9F6</RequestId><HostId>2mMzuUG6KxeUd+k2PJDgjsV83q5k8QV8UXwosCL+CKvyGRKUbR0iI69xGU5PSQ+Pz8nUyKp1I2M=</HostId></Error>
• For: Toolchain: https://onion-cdn.s3.amazonaws.com/community/openwrt/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar I get:
  This XML file does not appear to have any style information associated with it. The document tree is shown below.
  <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>2D9FE457B4300D92</RequestId><HostId>myrvYfcMVTDgO/AVEEKQZ6YlkkwzbmhP1G8M68YMUmv6zQi5wA18ittx5HL0neMsIVZyMMtIf98=</HostId></Error>

For the record, in case it is of help to others, this is what I ended up doing based largely on the info in:http://techfindings.one/archives/1487
For the record my host system for the compilation is a pretty standard KUbuntu-14.04 system running in a VM under VirtualBox

• Download the tool chain from https://s3-us-west-2.amazonaws.com/onion-cdn/community/openwrt/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar.bz2
• Unpack it to some suitable directory (referred to below as <tc_dir>)
• Set up environment variables as follows (I put this in my ~/.profile file so it was always there):
• • PATH=<tc_dir>/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin:$PATH
• • STAGING_DIR=<tc_dir>/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2
• • export STAGING_DIR
• Create your c program - e.g. test-prog.c
• Compile the program using (e.g.): mips-openwrt-linux-uclibc-gcc test-prog.c -o test-prog
• Transfer the output file (test-prog) to your Omega using you favourite tools.
• On the Omega in the directory you placed the file, run it by: ./test-prog - and there you are

I'm sure there will be other issues (e.g. using a makefile with multiple sources; access to libraries; building dynamic link libraries which I will want too), but these are all pretty standard development issues now that I have the code cross-compilation working.

A VM for virtual box would be more general, similar to what the C.H.I.P. people are doing.

Eventually the tool chain could plug into the Arduino IDE.

Can you explain what you mean by Arduino style library for Linux?