Re: [Buildroot] [PATCH 04/11] package/gmp: disable C++ bindings on m68k ColdFire

From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
	 Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	 Ismael Luceno <ismael@iodev.co.uk>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 04/11] package/gmp: disable C++ bindings on m68k ColdFire
Date: Fri, 29 May 2026 13:10:27 +0200	[thread overview]
Message-ID: <ahlwv5oXH7vzu4LX@windsurf> (raw)
In-Reply-To: <20260424132326.825570-5-jeanmichel.hautbois@yoseli.org>

On Fri, Apr 24, 2026 at 03:23:19PM +0200, Jean-Michel Hautbois wrote:
> On m68k ColdFire, libgcc.a exports __sync_* atomic built-in functions
> as hidden symbols. When GMP's C++ bindings are enabled, libgmpxx.so
> links against libstdc++ which references these hidden symbols, causing
> a linker error:
> 
>   hidden symbol '__sync_val_compare_and_swap_4' in libgcc.a is
>   referenced by DSO
> 
> Disable C++ bindings on m68k ColdFire. The C library (libgmp.so) is
> unaffected.

But isn't that a bug somewhere? Not sure if the bug is that libgcc.a
exports __sync built-ins as hidden symbols, or something else.

Also, why don't we see build failures on the autobuilders, for other
Coldfire processors? Is this affecting only your new Coldfire CPU, or
also other ones?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot