From: Avi Kivity <avi@scylladb.com>
To: "Rafael Ávila de Espíndola" <espindola@scylladb.com>,
seastar-dev@googlegroups.com
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [seastar-dev] [PATCH] mk: avoid combining -r and -export-dynamic linker options
Date: Mon, 27 Jan 2020 10:30:57 +0200 [thread overview]
Message-ID: <5ab62801-ee49-d01c-2835-65b631b726b4@scylladb.com> (raw)
In-Reply-To: <20200127013307.22633-1-espindola@scylladb.com>
On 27/01/2020 03.33, Rafael Ávila de Espíndola wrote:
> Running ld with -r switches the linker to a very special mode where
> some other linker options don't make sense.
>
> In particular, -export-dynamic normally requires that all global
> symbols be included in the dynamic symbol table, but a .o file doesn't
> even have a dynamic symbol table.
>
> When given both options it looks like the gnu linker just ignores
> -export-dynamic.
>
> Unfortunately some versions of lld (https://lld.llvm.org/) have a bug
> that causes it to try to create a dynamic symbol table in the output
> .o file and ends up corrupting it
> (https://bugs.llvm.org/show_bug.cgi?id=43552). Current (git) version
> of lld now issues an error.
>
> This patch filters out -export-dynamic from $(LDFLAGS) when using
> -r. With this patch I can build dpdk with lld.
>
> Fixes: 3d781ca32874 ("mk: do post processing on objects that register a driver")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rafael Ávila de Espíndola <espindola@scylladb.com>
> (cherry picked from commit 5a352a3a98e3297555cb08d2db6e45a93ce7e058)
> ---
> Once seastar is updated to use this it should be possible to build
> seastar and scylla with lld, which might help with the bots running
> out of resources during the link.
That turned out to be a configuration problem (docker was limited to a
small number of tasks, and multithreaded linking overflowed it).
Not to say we shouldn't support lld, of course.
> mk/internal/rte.compile-pre.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mk/internal/rte.compile-pre.mk b/mk/internal/rte.compile-pre.mk
> index 0cf3791b4..82fe098f7 100644
> --- a/mk/internal/rte.compile-pre.mk
> +++ b/mk/internal/rte.compile-pre.mk
> @@ -61,7 +61,7 @@ CHECK_EXPERIMENTAL = $(EXPERIMENTAL_CHECK) $(SRCDIR)/$(EXPORT_MAP) $@
>
> PMDINFO_GEN = $(RTE_SDK_BIN)/app/dpdk-pmdinfogen $@ $@.pmd.c
> PMDINFO_CC = $(CC) $(CPPFLAGS) $(CFLAGS) $(EXTRA_CFLAGS) -c -o $@.pmd.o $@.pmd.c
> -PMDINFO_LD = $(CROSS)ld $(LDFLAGS) -r -o $@.o $@.pmd.o $@
> +PMDINFO_LD = $(CROSS)ld -r $(filter-out -export-dynamic,$(LDFLAGS)) -o $@.o $@.pmd.o $@
> PMDINFO_TO_O = if grep -q 'RTE_PMD_REGISTER_.*(.*)' $<; then \
> echo "$(if $V,$(PMDINFO_GEN), PMDINFO $@.pmd.c)" && \
> $(PMDINFO_GEN) && \
next prev parent reply other threads:[~2020-01-28 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 1:33 [dpdk-stable] " Rafael Ávila de Espíndola
2020-01-27 8:30 ` Avi Kivity [this message]
2020-01-27 8:34 ` [dpdk-stable] [seastar-dev] " Avi Kivity
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=5ab62801-ee49-d01c-2835-65b631b726b4@scylladb.com \
--to=avi@scylladb.com \
--cc=espindola@scylladb.com \
--cc=seastar-dev@googlegroups.com \
--cc=stable@dpdk.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).