From: Stephen Hemminger <stephen@networkplumber.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] build: fix build failure with -fno-common
Date: Mon, 20 Jan 2020 09:42:01 -0800 [thread overview]
Message-ID: <20200120094201.45323e5f@hermes.lan> (raw)
In-Reply-To: <20200108100424.26642-1-jengelh@inai.de>
On Wed, 8 Jan 2020 11:04:24 +0100
Jan Engelhardt <jengelh@inai.de> wrote:
> $ make CCOPTS=-fno-common
> gcc ... -o ip
> ld: rt_names.o (symbol from plugin): in function "rtnl_rtprot_n2a":
> (.text+0x0): multiple definition of "numeric"; ip.o (symbol from plugin):(.text+0x0): first defined here
>
> gcc ... -o tipc
> ld: ../lib/libutil.a(utils.o):(.bss+0xc): multiple definition of `pretty';
> tipc.o:tipc.c:28: first defined here
>
> References: https://bugzilla.opensuse.org/1160244
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>
Looks good, applied.
prev parent reply other threads:[~2020-01-20 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 10:04 [PATCH] build: fix build failure with -fno-common Jan Engelhardt
2020-01-20 17:42 ` Stephen Hemminger [this message]
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=20200120094201.45323e5f@hermes.lan \
--to=stephen@networkplumber.org \
--cc=jengelh@inai.de \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).