DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-ci] Please install libatomic on your systems
Date: Fri, 2 Jul 2021 12:31:47 -0400	[thread overview]
Message-ID: <CAOE1vsP2gpHxJa3fcT7OYYZ3SFELBRe49txFUfv5h892HbDN6Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xCNBL4yEZU0c=dJGYS+13QM7Uz7e2qnUkMuM7eaKKw+Q@mail.gmail.com>

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

Thanks David,

I've created an issue in our Jira to track this and we'll confirm when this
has been installed on all the systems in the UNH-IOL Community Lab.

Cheers,
Lincoln



On Fri, Jul 2, 2021 at 9:34 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hello all,
>
> This is a call for action for CI(s).
>
> Summary:
> It is not mandatory to install libatomic on *all* systems, but still
> recommended to avoid losing coverage on net/sfc.
> But it is *mandatory* if the ABI check is ran on this system.
>
>
> Details:
> The net/sfc driver will now depend on the libatomic package.
> This driver was always selected and built so far.
> But now, if libatomic is not installed, this driver won't be compiled
> anymore.
>
> Absence of this driver binary will be flagged as a failure by the ABI
> check: the check interprets a hw support removal as a ABI breakage.
>
> Example of output:
> ...
> [2727/2727] Linking target drivers/librte_event_octeontx2.so.21.3
> Error: cannot find librte_net_sfc.dump in
> /home/dmarchan/builds/build-gcc-shared/install
>
>
> --
> David Marchand
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 2647 bytes --]

  reply	other threads:[~2021-07-02 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 13:34 David Marchand
2021-07-02 16:31 ` Lincoln Lavoie [this message]
2021-07-07 11:18   ` David Marchand
2021-07-07 12:27     ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2021-07-07 17:51       ` Brandon Lo
2021-07-07 18:36         ` David Marchand
2021-07-15  8:00           ` David Marchand
2021-07-15 16:56             ` Brandon Lo

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=CAOE1vsP2gpHxJa3fcT7OYYZ3SFELBRe49txFUfv5h892HbDN6Q@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).