Questions[cross-compilation](ubuntu)

I'm trying to build a debian package for an ARM64 platform on my AMD64 Ubuntu OS. I execute the command

debuild -us -uc --host-arch arm64

but get the warning

dpkg-architecture: warning: specified GNU system type aarch64-linux-gnu does not match CC system type x86_64-linux-gnu, try setting a correct CC environment variable

and so would like to know how to set the CC environment variable, as the warning advises. For my target OS I would typically use

/opt/l4t-gcc-toolchain-64-bit-32.1/install/bin/aarch64-linux-gnu-gcc

Thanks.

I have some compilers for different architectures:

$ > whereis gcc
gcc: /usr/bin/gcc /usr/lib/gcc /usr/share/man/man1/gcc.1.gz

$ > whereis arm-linux-gnueabi-gcc
arm-linux-gnueabi-gcc: /usr/bin/arm-linux-gnueabi-gcc /usr/share/man/man1/arm-linux-gnueabi-gcc.1.gz

$ > whereis arm-linux-gnueabihf-gcc
arm-linux-gnueabihf-gcc: ~/.local/bin/arm-linux-gnueabihf-gcc

gcc is for my workstation. It was installed in system path.

arm-linux-gnueabi-gcc is for ARM target without hard float. It was installed in system path too.

arm-linux-gnueabihf-gcc is for ARM target with hard float. It was installed in my $(HOME)/.local/ directory. And I have added this directory to binary path in the .bashrc script:

export PATH="$HOME/.local/bin:$PATH"

The system command whereis works true for all this compilers and shows valid path to binary executable file.

I wanted to compile some project for ARM with help arm-linux-gnueabihf-gcc compiler, but I have received this:

as: unrecognised option '-mcpu=cortex-a53'

Error during assembler. Seems that my build system wish to use assembler for my x86, not arm-linux-gnueabihf-as.

After the installing arm-linux-gnueabihf to ~/.local into the one some directories are appeared:

 ~/.local> ls -l
arm-linux-gnueabihf/
bin/
gcc-linaro-5.3.1-2016.05-linux-manifest.txt
include/
lib/
libexec/
share/

If i will go to bin/ I will see the binbary files:

arm-linux-gnueabihf-addr2line*  arm-linux-gnueabihf-cpp*        arm-linux-gnueabihf-gcc-ar*      arm-linux-gnueabihf-gdb*       arm-linux-gnueabihf-nm*       arm-linux-gnueabihf-size*     isort*
arm-linux-gnueabihf-ar*         arm-linux-gnueabihf-elfedit*    arm-linux-gnueabihf-gcc-nm*      arm-linux-gnueabihf-gfortran*  arm-linux-gnueabihf-objcopy*  arm-linux-gnueabihf-strings*  pylint*
arm-linux-gnueabihf-as*         arm-linux-gnueabihf-g++*        arm-linux-gnueabihf-gcc-ranlib*  arm-linux-gnueabihf-gprof*     arm-linux-gnueabihf-objdump*  arm-linux-gnueabihf-strip*    pyreverse*
arm-linux-gnueabihf-c++*        arm-linux-gnueabihf-gcc*        arm-linux-gnueabihf-gcov*        arm-linux-gnueabihf-ld*        arm-linux-gnueabihf-ranlib*   epylint*                      runtest*
arm-linux-gnueabihf-c++filt*    arm-linux-gnueabihf-gcc-5.3.1*  arm-linux-gnueabihf-gcov-tool*   arm-linux-gnueabihf-ld.bfd*    arm-linux-gnueabihf-readelf*  gdbserver*                    symilar*

This path was added to $PATH.

But if i will go to ./arm-linux-gnueabihf/bin and will do ls, i will receive empty directory. I can overcome the error, if i will add some symbolic links to this directory:

ar -> ../../bin/arm-linux-gnueabihf-ar*
as -> ../../bin/arm-linux-gnueabihf-as*
gcc -> ../../bin/arm-linux-gnueabihf-gcc*
ranlib -> ../../bin/arm-linux-gnueabihf-ranlib*
strip -> ../../bin/arm-linux-gnueabihf-strip*
...

After this my assembler error disappears and I can successfully compile project for ARM-target. But after this I can't compile anything for my workstation x86.

Could anyone explain me what i should to do to successful compiling and for ARM and for x86, please?

UPD: I have the Makefile for ARM:

CROSS_COMPILE = arm-linux-gnueabihf-
CC            = $(CROSS_COMPILE)gcc
AS            = $(CROSS_COMPILE)as

INCLUDES      = -I./
SRC           = main.c
TARGET        = my-arm-target

all: $(SRC)
    $(CC) $(INCLUDES) -o $(TARGET)

And the same file for x86, but without CROSS_COMPILE variable:

CC            = gcc
AS            = as

INCLUDES      = -I./
SRC           = main.c
TARGET        = my-x86-target

all: $(SRC)
    $(CC) $(INCLUDES) -o $(TARGET)

I cross compiled a program on linux for MacOS and now I want that MacOS binary to convert to DMG file for MacOS.

Is there a way to convert a MacOS binary on Linux (Ubuntu) into DMG file for MacOS?

I have set up a cross-compile docker instance. In a nutshell I started setting up the

apt-get update
apt-get install binutils-multiarch

dpkg --add-architecture armhf
# Manually add correct armhf repositories to /etc/apt/sources.list
apt-get update
apt-get install libudev-dev:armhf

During this last step, I get the following error:

The following packages have unmet dependencies:
libudev-dev:armhf : Depends: libacl1:armhf (>= 2.2.51-8) but it is not going to be installed
                    Depends: libblkid1:armhf (>= 2.19.1) but it is not going to be installed
                    Depends: libc6:armhf (>= 2.17) but it is not going to be installed
                    Depends: libgcc1:armhf (>= 1:3.5) but it is not going to be installed
                    Depends: libkmod2:armhf (>= 5~) but it is not going to be installed
                    Depends: libselinux1:armhf (>= 2.0.65) but it is not going to be installed
                    Depends: libudev1:armhf (= 229-4ubuntu4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Installing these manually is not an option, since libc6:armhf conflicts with the currently installed amd64 libc6 and will end up overwriting this package. I just want to set-up the libudev:armhf package such that I can link to it.

/etc/apt/sources.list:

deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ xenial main restricted
deb [arch=armhf] http://ports.ubuntu.com/ubuntu-ports/ xenial main restricted

deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ xenial-updates main restricted

deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ xenial universe
deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ xenial-updates universe

deb [arch=amd64] http://security.ubuntu.com/ubuntu/ xenial-security main restricted
deb [arch=amd64] http://security.ubuntu.com/ubuntu/ xenial-security universe
deb [arch=amd64] http://security.ubuntu.com/ubuntu/ xenial-security multiverse

Running apt-cache policy libudev-dev:{amd64,armhf} outputs the following:

libudev-dev:
  Installed: (none)
  Candidate: 229-4ubuntu21.4
  Version table:
     229-4ubuntu21.4 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
     229-4ubuntu21.1 500
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
     229-4ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libudev-dev:armhf:
  Installed: (none)
  Candidate: 229-4ubuntu4
  Version table:
     229-4ubuntu4 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages

I have a large application I have written. I can successfully compile the application in the following scenarios:

• in a native compilation for the i386 host running Ubuntu 12.04
• natively on a PandaBoard running Ubuntu 12.04 (this takes a long time)
• using Qemu and a chroot on the host PC for the armhf PandaBoard target (this takes a very long time)

I would like to cross-compile the application on the i386 host to run on a target such as the PandaBoard to complete builds in a timely fashion. So far attempts made using the arm-linux-gnueabihf tool chain in the repositories has produced binaries that do not run correctly. At this stage, I have no plans to package the software.

What is the recommended way to achieve a successful cross-compile?