spdk.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] nasm on test machines
Date: Mon, 20 Aug 2018 13:09:27 +0000	[thread overview]
Message-ID: <C159D0CD-F87E-41B5-90FC-E74F403A4891@intel.com> (raw)
In-Reply-To: 82C9F782B054C94B9FC04A331649C77AAD51ABBE@fmsmsx104.amr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 2964 bytes --]

Adding nasm to pkgdep.sh may not be sufficient.  It needs to be a new enough version which supports instructions used by IPSec library.

Jim

Sent from my iPhone

> On Aug 20, 2018, at 5:50 AM, Luse, Paul E <paul.e.luse(a)intel.com> wrote:
> 
> Yeah, probably so..  Will see what others think.  I have another patch out that also updated pkgdep to install the ipsec lib since it takes root (ugh).  https://review.gerrithub.io/c/spdk/intel-ipsec-mb/+/422747  Once that lands it will need to be run on the test machines also.  See what Jim, Ben & the others say about adding name to the script.
> 
> Thanks Karol!
> 
> -Paul
> 
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Latecki, Karol
> Sent: Monday, August 20, 2018 4:05 AM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: Re: [SPDK] nasm on test machines
> 
> Hi Paul!
> Installed on machines on my side.
> I think you should add it to pkgdep.sh if it's needed for any of ./configure options.
> 
> Karol
> 
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
> Sent: Saturday, August 18, 2018 6:37 PM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: [SPDK] nasm on test machines
> 
> Seth/Karol,
> 
> Can we get nasm (see below) installed on all the test machines (& VMs)?  Right now it's not in pkgdep.sh but I'm wondering if it should be now... see https://review.gerrithub.io/c/spdk/spdk/+/422746
> 
> FYI this if for crypto (well for ipsesc lib which is needed for crypto)
> 
> Thx
> Paul
> 
> NASM version 2.12.02 or newer
> 
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
> --------------------------------------------------------------------
> 
> Intel Technology Poland sp. z o.o.
> ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
> 
> Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
> This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
> 
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

             reply	other threads:[~2018-08-20 13:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 13:09 Harris, James R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-28 20:04 [SPDK] nasm on test machines Luse, Paul E
2018-08-21 21:24 Luse, Paul E
2018-08-21 15:49 Howell, Seth
2018-08-20 21:19 Luse, Paul E
2018-08-20 15:08 Harris, James R
2018-08-20 13:44 Luse, Paul E
2018-08-20 13:42 Luse, Paul E
2018-08-20 13:32 Harris, James R
2018-08-20 13:14 Luse, Paul E
2018-08-20 12:47 Luse, Paul E
2018-08-20 11:05 Latecki, Karol
2018-08-18 16:36 Luse, Paul E

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=C159D0CD-F87E-41B5-90FC-E74F403A4891@intel.com \
    --to=spdk@lists.01.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).