From: Bruce Richardson <bruce.richardson@intel.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: Re: PIE static library builds
Date: Tue, 14 Mar 2023 16:29:43 +0000 [thread overview]
Message-ID: <ZBCg9ydmVGyM+3Nv@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <e164b124-f565-21f4-ba42-ade4fd54282c@lysator.liu.se>
On Tue, Mar 14, 2023 at 05:22:02PM +0100, Mattias Rönnblom wrote:
> Hi.
>
> Is the "b_staticpic" meson build option supposed to work with DPDK?
>
> Setting it to "false" (default is "true") causes link failures on Ubuntu
> 22.04, with GCC 9 and 11, on v23.03rc1 and v22.11:
>
> /usr/bin/ld: lib/librte_eal.a.p/eal_common_eal_common_errno.c.o: relocation
> R_X86_64_TPOFF32 against `per_lcore_retval.1' can not be used when making a
> shared object; recompile with -fPIC
> /usr/bin/ld: failed to set dynamic section sizes: bad value
> collect2: error: ld returned 1 exit status
>
> Does something per-lcore/TLS-related require PIC builds, even for static
> libraries?
>
I don't think that is the issue. The "issue" is that DPDK always does both
static and shared builds from the same object files, so without -fPIC the
shared library parts of the build fails. To support not using staticpic,
we'd have to disable building the .so's in those cases, or each C file
built twice.
/Bruce
next prev parent reply other threads:[~2023-03-14 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 16:22 Mattias Rönnblom
2023-03-14 16:29 ` Bruce Richardson [this message]
2023-03-14 18:04 ` Mattias Rönnblom
2023-03-14 18:31 ` Bruce Richardson
2023-03-15 14:18 ` Bruce Richardson
2023-03-15 15:45 ` Mattias Rönnblom
2023-03-15 15:55 ` Bruce Richardson
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=ZBCg9ydmVGyM+3Nv@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--cc=mattias.ronnblom@ericsson.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;
as well as URLs for NNTP newsgroup(s).