The primary target of the Ubuntu arm-linux-gnueabi cross compiler is to compile for a different architecture of the same Ubuntu release leveraging the Debian/Ubuntu multiarch capabilities. Example: You compile on Ubuntu 16.04 amd64 for Ubuntu 16.04 armel.

If you would like to do a similar thing for Raspbian I suggest the following approach:

• On your Ubuntu host install Debian Jessie amd64 within a chroot or a LXC container.
• Enable the foreign architecture armhf.
• Install the cross compiler from the emdebian tools repository.
• Tweak the cross compiler (it would generate code for ARMv7-A by default) by writing a custom gcc specs file.
• Install armhf libraries (libstdc++ etc.) from the Raspbian repository.
• Build your source code.

Since this is a lot of work I have automated the above setup. You can read about it here: http://www.get-edi.io/Cross-Compiling-for-Raspbian/

I'm gonna try to write this as a tutorial for you so it becomes easy to follow.

NOTE: This tutorial only works for older raspbian images. For the newer Raspbian based on Debian Buster see the following how-to in this thread: https://stackoverflow.com/a/58559140/869402

Pre-requirements

Before you start you need to make sure the following is installed:

apt-get install git rsync cmake libc6-i386 lib32z1 lib32stdc++6

Let's cross compile a Pie!

Start with making a folder in your home directory called raspberrypi.

Go in to this folder and pull down the ENTIRE tools folder you mentioned above:

git clone git://github.com/raspberrypi/tools.git

You wanted to use the following of the 3 ones, gcc-linaro-arm-linux-gnueabihf-raspbian, if I did not read wrong.

Go into your home directory and add:

export PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin

to the end of the file named ~/.bashrc

Now you can either log out and log back in (i.e. restart your terminal session), or run . ~/.bashrc in your terminal to pick up the PATH addition in your current terminal session.

Now, verify that you can access the compiler arm-linux-gnueabihf-gcc -v. You should get something like this:

Using built-in specs.
COLLECT_GCC=arm-linux-gnueabihf-gcc
COLLECT_LTO_WRAPPER=/home/tudhalyas/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/../libexec/gcc/arm-linux-gnueabihf/4.7.2/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: /cbuild/slaves/oort61/crosstool-ng/builds/arm-linux-gnueabihf-raspbian-linux/.b
 uild/src/gcc-linaro-4.7-2012.08/configure --build=i686-build_pc-linux-gnu --host=i686-build_pc-
 linux-gnu --target=arm-linux-gnueabihf --prefix=/cbuild/slaves/oort61/crosstool-ng/builds/arm-l
 inux-gnueabihf-raspbian-linux/install --with-sysroot=/cbuild/slaves/oort61/crosstool-ng/builds/
 arm-linux-gnueabihf-raspbian-linux/install/arm-linux-gnueabihf/libc --enable-languages=c,c++,fo
 rtran --disable-multilib --with-arch=armv6 --with-tune=arm1176jz-s --with-fpu=vfp --with-float=
 hard --with-pkgversion='crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08' --with-bugurl=
 https://bugs.launchpad.net/gcc-linaro --enable-__cxa_atexit --enable-libmudflap --enable-libgom
 p --enable-libssp --with-gmp=/cbuild/slaves/oort61/crosstool-ng/builds/arm-linux-gnueabihf-rasp
 bian-linux/.build/arm-linux-gnueabihf/build/static --with-mpfr=/cbuild/slaves/oort61/crosstool-
 ng/builds/arm-linux-gnueabihf-raspbian-linux/.build/arm-linux-gnueabihf/build/static --with-mpc
 =/cbuild/slaves/oort61/crosstool-ng/builds/arm-linux-gnueabihf-raspbian-linux/.build/arm-linux-
 gnueabihf/build/static --with-ppl=/cbuild/slaves/oort61/crosstool-ng/builds/arm-linux-gnueabihf
 -raspbian-linux/.build/arm-linux-gnueabihf/build/static --with-cloog=/cbuild/slaves/oort61/cros
 stool-ng/builds/arm-linux-gnueabihf-raspbian-linux/.build/arm-linux-gnueabihf/build/static --wi
 th-libelf=/cbuild/slaves/oort61/crosstool-ng/builds/arm-linux-gnueabihf-raspbian-linux/.build/a
 rm-linux-gnueabihf/build/static --with-host-libstdcxx='-L/cbuild/slaves/oort61/crosstool-ng/bui
 lds/arm-linux-gnueabihf-raspbian-linux/.build/arm-linux-gnueabihf/build/static/lib -lpwl' --ena
 ble-threads=posix --disable-libstdcxx-pch --enable-linker-build-id --enable-plugin --enable-gol
 d --with-local-prefix=/cbuild/slaves/oort61/crosstool-ng/builds/arm-linux-gnueabihf-raspbian-li
 nux/install/arm-linux-gnueabihf/libc --enable-c99 --enable-long-long
Thread model: posix
gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08
 )

But hey! I did that and the libs still don't work!

We're not done yet! So far, we've only done the basics.

In your raspberrypi folder, make a folder called rootfs.

Now you need to copy the entire /liband /usr directory to this newly created folder. I usually bring the rpi image up and copy it via rsync:

rsync -rl --delete-after --safe-links [email protected]:/{lib,usr} $HOME/raspberrypi/rootfs

where 192.168.1.PI is replaced by the IP of your Raspberry Pi.

Now, we need to write a cmake config file. Open ~/home/raspberrypi/pi.cmake in your favorite editor and insert the following:

SET(CMAKE_SYSTEM_NAME Linux)
SET(CMAKE_SYSTEM_VERSION 1)
SET(CMAKE_C_COMPILER $ENV{HOME}/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc)
SET(CMAKE_CXX_COMPILER $ENV{HOME}/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-g++)
SET(CMAKE_FIND_ROOT_PATH $ENV{HOME}/raspberrypi/rootfs)
SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

Now you should be able to compile your cmake programs simply by adding this extra flag: -D CMAKE_TOOLCHAIN_FILE=$HOME/raspberrypi/pi.cmake.

Using a cmake hello world example:

git clone https://github.com/jameskbride/cmake-hello-world.git 
cd cmake-hello-world
mkdir build
cd build
cmake -D CMAKE_TOOLCHAIN_FILE=$HOME/raspberrypi/pi.cmake ../
make
scp CMakeHelloWorld [email protected]:/home/pi/
ssh [email protected] ./CMakeHelloWorld

I cross-compiled your code, and did not run into a Segmentation Fault. Here is what my setup looks like - maybe it helps you getting yours to run. For Cross-Compilation from my Ubuntu 64-bit to my Raspberry Pi B+ (which has the same architecture like the Pi-Zero (ARMv6)) I used the raspberry tools.

I usually use CodeBlocks to do the compilation for me. But for you, I tried it with a makefile which looks like:

 hello-world :  hello-world.c
    /PATH_TO_THE_RPI_TOOLS/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-gcc -o  hello-world  hello-world.c

After running make, I copyed the executable to the pi, changed the permissions to -rwxr--r-- and run the program with:

./hello-world

Check out this guide from Jeff Geerling. He does a lot of work on the Raspberry Pi and has setup kernel cross compiling on his macbook.

https://github.com/geerlingguy/raspberry-pi-pcie-devices/tree/master/extras/cross-compile

https://www.youtube.com/c/JeffGeerling/

Hi Jorj,

I'm having trouble to install MuPDF. Below is the error I have when I run make prefix=/usr/local install:

pi@pi:/gcc_all/mupdf $ make prefix=/usr/local install
CC build/debug/pdf/pdf-pkcs7.o
source/pdf/pdf-pkcs7.c: In function ‘bsegs_read’:
source/pdf/pdf-pkcs7.c:30:39: error: dereferencing pointer to incomplete type ‘BIO’ {aka ‘struct bio_st’}
BIO_SEGS_CTX *ctx = (BIO_SEGS_CTX *)b->ptr;
^~
source/pdf/pdf-pkcs7.c: At top level:
source/pdf/pdf-pkcs7.c:107:1: error: variable ‘methods_bsegs’ has initializer but incomplete type
static BIO_METHOD methods_bsegs =
^~~~~~
source/pdf/pdf-pkcs7.c:109:2: warning: excess elements in struct initializer
0,"segment reader",
^
source/pdf/pdf-pkcs7.c:109:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:109:4: warning: excess elements in struct initializer
0,"segment reader",
^~~~~~~~~~~~~~~~
source/pdf/pdf-pkcs7.c:109:4: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:110:2: warning: excess elements in struct initializer
NULL,
^~~~
source/pdf/pdf-pkcs7.c:110:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:111:2: warning: excess elements in struct initializer
bsegs_read,
^~~~~~~~~~
source/pdf/pdf-pkcs7.c:111:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:112:2: warning: excess elements in struct initializer
NULL,
^~~~
source/pdf/pdf-pkcs7.c:112:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:113:2: warning: excess elements in struct initializer
NULL,
^~~~
source/pdf/pdf-pkcs7.c:113:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:114:2: warning: excess elements in struct initializer
bsegs_ctrl,
^~~~~~~~~~
source/pdf/pdf-pkcs7.c:114:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:115:2: warning: excess elements in struct initializer
bsegs_new,
^~~~~~~~~
source/pdf/pdf-pkcs7.c:115:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:116:2: warning: excess elements in struct initializer
bsegs_free,
^~~~~~~~~~
source/pdf/pdf-pkcs7.c:116:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:117:2: warning: excess elements in struct initializer
bsegs_callback_ctrl,
^~~~~~~~~~~~~~~~~~~
source/pdf/pdf-pkcs7.c:117:2: note: (near initialization for ‘methods_bsegs’)
source/pdf/pdf-pkcs7.c:135:17: error: field ‘x509_ctx’ has incomplete type
X509_STORE_CTX x509_ctx;
^~~~~~~~
source/pdf/pdf-pkcs7.c: In function ‘verify_callback’:
source/pdf/pdf-pkcs7.c:159:13: error: dereferencing pointer to incomplete type ‘X509_STORE_CTX’ {aka ‘struct x509_store_ctx_st’}
switch (ctx->error)
^~
source/pdf/pdf-pkcs7.c: In function ‘pk7_verify’:
source/pdf/pdf-pkcs7.c:208:40: error: dereferencing pointer to incomplete type ‘X509_STORE’ {aka ‘struct x509_store_st’}
X509_VERIFY_PARAM_set_flags(cert_store->param, X509_V_FLAG_CB_ISSUER_CHECK);
^~
source/pdf/pdf-pkcs7.c: At top level:
source/pdf/pdf-pkcs7.c:107:19: error: storage size of ‘methods_bsegs’ isn’t known
static BIO_METHOD methods_bsegs =
^~~~~~~~~~~~~
source/pdf/pdf-pkcs7.c: In function ‘bsegs_ctrl’:
source/pdf/pdf-pkcs7.c:66:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
source/pdf/pdf-pkcs7.c: In function ‘bsegs_callback_ctrl’:
source/pdf/pdf-pkcs7.c:105:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
make: [Makefile:136: build/debug/pdf/pdf-pkcs7.o] Error 1

Would installing 64bits Raspian solve these issues?