From: "Zhou, YidingX" <yidingx.zhou@intel.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 19.11] net/iavf: add thread for event callbacks
Date: Wed, 16 Nov 2022 09:58:27 +0000 [thread overview]
Message-ID: <DM5PR1101MB210798AAD460B6007B94ED5F85079@DM5PR1101MB2107.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM5PR1101MB21078D157F2A267FA10FD39285079@DM5PR1101MB2107.namprd11.prod.outlook.com>
> > -----Original Message-----
> > From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > Sent: Wednesday, November 16, 2022 4:18 PM
> > To: Zhou, YidingX <yidingx.zhou@intel.com>
> > Cc: stable@dpdk.org
> > Subject: Re: [PATCH 19.11] net/iavf: add thread for event callbacks
> >
> > On Wed, Nov 16, 2022 at 3:35 AM Yiding Zhou <yidingx.zhou@intel.com>
> wrote:
> > >
> > > [upstream commit cb5c1b91f76f436724cd09f26c7432b2775b519c]
> >
> > Hi,
> > I tried to apply this but it causes build errors:
> >
> > [ 151s] iavf_vchnl.o: In function `iavf_dev_event_handler_fini':
> > [ 151s] iavf_vchnl.c:(.text+0x5d9): undefined reference to `pthread_cancel'
> > [ 151s] iavf_vchnl.c:(.text+0x611): undefined reference to `pthread_join'
> > [ 151s] collect2: error: ld returned 1 exit status [ 151s] make[4]:
> > *** [librte_pmd_iavf.so.20.0] Error 1 [ 151s] make[3]: *** [iavf]
> > Error 2
> >
> > On all redhat, fedora, suse builds.
> > Interestingly the Ubuntu builds worked fine, but only them.
> >
> > Please have a look and resubmit.
> >
> Ok, I will check this on other systems.
Hi
I have built DPDK successfully on the following systems.
OS: Fedora release 36 (Thirty Six)
meson: 0.63.1
ninja: 1.10.2.git.kitware.jobserver-1
gcc: gcc (GCC) 12.2.1 20220819 (Red Hat 12.2.1-1)
----------------
OS: SUSE Linux Enterprise Server 15 SP4 (x86_64)
meson: n0.61.5
ninja: 1.10.2.git.kitware.jobserver-1
gcc: gcc (SUSE Linux) 7.5.0
----------------
OS: Red Hat Enterprise Linux release 9.0 (Plow)
meson: 0.63.2
ninja: 1.10.2.git.kitware.jobserver-1
gcc: gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9)
What is your build environment?
next prev parent reply other threads:[~2022-11-16 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 2:39 Yiding Zhou
2022-11-16 8:17 ` Christian Ehrhardt
[not found] ` <DM5PR1101MB21078D157F2A267FA10FD39285079@DM5PR1101MB2107.namprd11.prod.outlook.com>
2022-11-16 9:58 ` Zhou, YidingX [this message]
2022-11-17 7:47 ` Christian Ehrhardt
2022-11-17 9:05 ` Zhou, YidingX
2022-11-17 9:14 ` Christian Ehrhardt
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=DM5PR1101MB210798AAD460B6007B94ED5F85079@DM5PR1101MB2107.namprd11.prod.outlook.com \
--to=yidingx.zhou@intel.com \
--cc=christian.ehrhardt@canonical.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).