-
You get an error similar to:
No rule to make target `/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib32//crtendS.o', needed by ...
-
You are using a 64bit based host system; please install
a 32bit build environment.
On Debian/Ubuntu the package is
g++-multilib.
[Jun 2010]
-
You get an error similar to:
No rule to make target `..../lib/gcc/arm-none-eabi/4.5.2/crtendS.o, needed by ...
-
You're building for ARM. Please use the Linux target variant of gcc, e.g. arm-none-linux-gnueabi.
[May 2011]
-
Fiasco stops at 'Calibrating timer loop...'
-
You are using KVM and have Fiasco configured to use the PIT as the scheduler source:
Add -no-kvm-pit to the qemu-kvm command line.
[Aug 2010]
-
The build process spaws endless recursive make instances
-
You're using ecryptfs. You cannot build on ecryptfs (currently?), please
use some other filesystem, such as ext4.
[Oct 2010]
-
Link errors similar to:
/usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `.L107': (.text+0xb79): undefined reference to `__stack_chk_fail_local'
-
You're using Fedora/Redhat. Currently, consider switchting to Debian.
[Nov 2010]
-
You're getting:
ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1//crtbeginS.o' is incompatible with i386 output
ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1//crtendS.o' is incompatible with i386 output
-
Install the
g++-multilib (Debian/Ubuntu) package or equivalent.
-
You're seeing the following when building for x86_64/amd64:
==> Linking bootstrap32.elf
/usr/bin/ld: skipping incompatible
/usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
collect2: error: ld returned 1 exit status
-
Install the
g++-multilib (Debian/Ubuntu) package or equivalent.
[Feb 2014]
-
You're seeing the following when building:
... Building Dependencies
Invalid byte sequence in conversion input
-
This is an issue with pkg-config, a tool that is used by the build process.
You likely have an non-ascii character in your path (such as an Umlaut,
UTF8). For now, avoid UTF8 characters in paths. The issue has been reported.
[Nov 2014]