This is the mail archive of the
mailing list for the GCC project.
Re: multiple definition of symbols" when linking executables on ARM32 and AArch64
- From: Matthias Klose <doko at ubuntu dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: binutils <binutils at sourceware dot org>, GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Mon, 6 Jan 2020 11:56:24 +0100
- Subject: Re: multiple definition of symbols" when linking executables on ARM32 and AArch64
- References: <email@example.com> <CA+=Sn1=99WL03+833HqC5dNspt8ELCTR1MgqrL2AiX2naqqGBA@mail.gmail.com>
On 06.01.20 11:03, Andrew Pinski wrote:
> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose <firstname.lastname@example.org> wrote:
>> In an archive test rebuild with binutils and GCC trunk, I see a lot of build
>> failures on both aarch64-linux-gnu and arm-linux-gnueabihf failing with
>> "multiple definition of symbols" when linking executables, e.g.
> THIS IS NOT A BINUTILS OR GCC BUG.
> GCC changed the default to -fno-common.
> It seems like for some reason, your non-aarch64/arm builds had changed
> the default back to being with -fcommon turned on.
what would that be? I'm not aware of any active change doing that. Packages
build on x86, ppc64el and s390x at least.