From: "Adrian Bunk" <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] libunwind: Use -fcommon option to compile
Date: Wed, 5 Aug 2020 12:26:10 +0300 [thread overview]
Message-ID: <20200805092610.GA27769@localhost> (raw)
In-Reply-To: <20200805061449.1029166-1-raj.khem@gmail.com>
On Tue, Aug 04, 2020 at 11:14:48PM -0700, Khem Raj wrote:
> defaults for gcc is to use -fno-common this ensures that it keeps using
> -fcommon until the real issue is fixed
>
> Fixes
> src/arm/Ginit.c:60: multiple definition of `_U_dyn_info_list'; mi/.libs/dyn-info-list.o:/usr/src/debug/libunwind/1.4.0-r0/build/src/../../libunwind-1.4.0/src/mi/dyn-info-list.c:28: first defined here
>...
The upstream fix is
https://github.com/libunwind/libunwind/commit/29e17d8d2ccbca07c423e3089a6d5ae8a1c9cb6e
cu
Adrian
next prev parent reply other threads:[~2020-08-05 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 6:14 [PATCH 1/2] libunwind: Use -fcommon option to compile Khem Raj
2020-08-05 6:14 ` [PATCH 2/2] dhcp: Use -fcommon compiler option Khem Raj
2020-08-05 9:26 ` Adrian Bunk [this message]
2020-08-05 16:53 ` [OE-core] [PATCH 1/2] libunwind: Use -fcommon option to compile Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200805092610.GA27769@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox