From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ZUC PMD as shared library
Date: Wed, 12 Oct 2016 02:23:46 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973CA07CC6@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1537716.E2UdgpDg0I@xps13>
Hi Thomas,
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Saturday, October 08, 2016 10:19 AM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: ZUC PMD as shared library
>
> Hi Pablo,
>
> You are probably aware of the issue, but I would like to make it clear
> in case someone else run into the same trouble:
>
> It is impossible to build the ZUC crypto PMD as a shared library:
>
> libsso-zuc-0.1.1/build/libsso_zuc.a(sso_zuc_yasm.o):
> relocation R_X86_64_32 against `EK_d' can not be used
> when making a shared object; recompile with -fPIC
>
> The library libsso-zuc-0.1.1 needs an update to make the asm code
> relocatable.
> Should we explicit this limitation in the PMD doc?
Sorry for not replying to this earlier.
Yes, you are right, thanks for pointing it out.
I think the same problem is in KASUMI, so I will send a doc update for both PMDs.
Thanks,
Pablo
next prev parent reply other threads:[~2016-10-12 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 17:19 Thomas Monjalon
2016-10-12 2:23 ` De Lara Guarch, Pablo [this message]
2016-10-12 7:22 ` Thomas Monjalon
2016-10-13 18:30 ` De Lara Guarch, Pablo
2017-04-04 12:15 Thomas Monjalon
2017-04-05 9:46 ` De Lara Guarch, Pablo
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=E115CCD9D858EF4F90C690B0DCB4D8973CA07CC6@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).