This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/68467] libgcc, compilation for target m68k-linux breaks in linux_atomic.c
- From: "wbx at openadk dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 04 Dec 2016 11:35:09 +0000
- Subject: [Bug target/68467] libgcc, compilation for target m68k-linux breaks in linux_atomic.c
- Auto-submitted: auto-generated
- References: <bug-68467-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68467
--- Comment #11 from Waldemar Brodkorb <wbx at openadk dot org> ---
I talking about following change:
diff -Nur gcc.orig/libgcc/config.host gcc/libgcc/config.host
--- gcc.orig/libgcc/config.host 2016-02-26 21:02:28.000000000 +0100
+++ gcc/libgcc/config.host 2016-04-29 09:18:40.377989160 +0200
@@ -812,7 +812,7 @@
m68k*-*-openbsd*)
;;
m68k-*-uclinux*) # Motorola m68k/ColdFire running uClinux with uClibc
- tmake_file="$tmake_file m68k/t-floatlib m68k/t-linux"
+ tmake_file="$tmake_file m68k/t-floatlib"
md_unwind_header=m68k/linux-unwind.h
;;
m68k-*-linux*) # Motorola m68k's running GNU/Linux
This would allow to create a working toolchain.
m68k-nommu (coldfire) is only supported by uClibc-ng and not GNU libc.
There is only support for Linuxthreads, so TLS/libatomic is disabled at
configure time.
C++ support still seems to work fine.
The m68k (full MMU) support isn't changed with this patch.
>From the embedded build system maintainer view, I think the patch is fine to at
least
get some working toolchain until the ICE is solved.
The patch is used for some time in Buildroot/OpenADK.