cross-compiler | Dockerfiles for cross compiling environments | Continuous Deployment library

The issue was mentioned by @AnttiHaapala: By the instructions ask you to set the prefix to /usr/local/i386elfgcc - maybe you've accidentally dropped this out from the binutils config and installed binutils in /usr/bin instead

The solution was uninstalling the binutils and install it again

• sudo apt-get remove binutils

  sudo apt-get remove --auto-remove binutils

  sudo apt install build-essential

Now the binutils version is 2.34, earlier it was 2.24

Try doing brew update-reset. Do make a note of the following, however:

You linker commands are buggy because you misplaced the -no-PIE option.

Instead of ld -o -no-PIE $@, write ld -o $@ -no-PIE:

You're cross-compiling to a different architecture (i686-elf) than whatever you're running on—the $TARGET mentioned in the question. gdb will have to be linked with libraries which are built for that architecture.

Debian provides ncurses packages which run on the current architecture, but does not provide a suitable package for the cross-compiled application. So you get to do this for yourself.

When cross-compiling ncurses, you'll have to keep in mind that part of it builds/runs on the current architecture (to generate source-files for compiling by the cross-compiler). That's defined in the environment as $BUILD_CC (rather than $CC), as you might see when reading the script for the mingw cross-compiling. There's a section in the INSTALL file (in the ncurses sources) which outlines the process.

There's no tutorial (that would be off-topic here anyway), but others have read the instructions and cross-compiled ncurses as evidenced by a recent bug report.

I fixed it. I simply disabled multilib, because I can just simply build another compiler for 32-bit.

The cause for the errors is that gcc is running the native assembler instead of the or1200 one. Turns out the executable binary of the assembler was on a big file system with 64 bit inodes and happened to get one which was outside of the 32 bit integer range. gcc uses the stat C library function to locate the helper programs which in this case failed with EOVERFLOW. Unfortunately, the system call succeeds so looking in strace does not give a hint as to why the presence of the file is not detected:

It's what it says: you didn't define your member function when you declared it constexpr.

You must provide the definition immediately, inline in the class definition.

You can use one of the toolchains provided by ARM for your RPI3/4. If you are running a 32 bit Linux on your RPI3/4, use one of the arm-none-linux-gnueabihf toolchains, if use are running a 64 bit Linux on your RPI3/4, use one of the aarch64-none-linux-gnu one.

Both 10.2 and 9.2 versions of the two toolchains are working fine on my own Ubuntu 20.04.1 LTS x86_64 system. Of course, you can cross-compile programs with the arm-none-linux-gnueabihf toolchain and run them on the 64 bit Linux running on your RPI3/4 as well.

I did python 2.7.3 a while ago. The summary is here. All other files are in the same directory as this txt summary. Not sure whether it still works or not on ubuntu 20. Though it was for arm v5, you'll need to do some adjustment.

Any version after 2.7.3 uses a dramatically different build system. The same was not working. I'm looking for instructions to build 3.8.

Update: If you want to build python 3.8.6, I saw someone mentioned on SO about using buildroot. Here is a note that works. I've created a virtual env using it on the target device.