Re: [Buildroot] [PATCH 05/11] package/gdb: use static libgcc 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 05/11] package/gdb: use static libgcc on m68k ColdFire
Date: Fri, 29 May 2026 13:12:10 +0200	[thread overview]
Message-ID: <ahl0QDec-S1DSz4Y@windsurf> (raw)
In-Reply-To: <20260424132326.825570-6-jeanmichel.hautbois@yoseli.org>

Hello,

On Fri, Apr 24, 2026 at 03:23:20PM +0200, Jean-Michel Hautbois wrote:
> On m68k ColdFire, libgcc.a exports __sync_* atomic built-in functions
> as hidden symbols. GDB links against libstdc++ which references these
> symbols, causing linker errors when building as a dynamically linked
> executable.
> 
> Use -static-libstdc++ and -static-libgcc to avoid the hidden symbol
> issue.

A bit the same comment as on the previous patch. Is this an inherent
limitation? A bug?

Is this affecting all Coldfire processors? Only the brand new one?

Thanks!

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