From: David Marchand <david.marchand@redhat.com>
To: Mark de Roussier <mark@hitomi-broadcast.tv>
Cc: "Дмитрий Степанов" <stepanov.dmit@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: Couple of build problems ( Fedora 36, DPDK 21.11.1 )
Date: Wed, 20 Jul 2022 18:25:00 +0200 [thread overview]
Message-ID: <CAJFAV8zOaDvtcboJMiLG3RazbVQQrW5pB6mqEui1_3Fej70Yaw@mail.gmail.com> (raw)
In-Reply-To: <LO3P123MB328937147A99C4EA1874E6748F8E9@LO3P123MB3289.GBRP123.PROD.OUTLOOK.COM>
On Wed, Jul 20, 2022 at 6:12 PM Mark de Roussier
<mark@hitomi-broadcast.tv> wrote:
>
> >then maybe you did not reconfigure your build env.
> >$ meson --reconfigure <build_dir>
>
> 🙂. I tried many meson commands to wipe/reconfigure my build environment, but I've just blown away the whole build directory and started again, and now it appears to be working ( though I thought I'd tried that before too ). Maybe I missed a trick with reconfiguring meson, I don't know. The PC has also been restarted a few times. The ninja build succeeds ( with warnings ).
Those warnings may be what I have fixed in 22.07 wrt GCC 12.
Backports for 21.11 are in progress, you may try with the last
stable/21.11 branch.
https://git.dpdk.org/dpdk-stable/log/?h=21.11
--
David Marchand
next prev parent reply other threads:[~2022-07-20 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 8:38 Mark de Roussier
2022-07-20 9:55 ` Дмитрий Степанов
2022-07-20 12:19 ` Mark de Roussier
2022-07-20 14:14 ` David Marchand
2022-07-20 14:58 ` Mark de Roussier
2022-07-20 15:18 ` David Marchand
2022-07-20 16:12 ` Mark de Roussier
2022-07-20 16:25 ` David Marchand [this message]
2022-07-20 15:37 ` Dmitry Kozlyuk
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=CAJFAV8zOaDvtcboJMiLG3RazbVQQrW5pB6mqEui1_3Fej70Yaw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=mark@hitomi-broadcast.tv \
--cc=stepanov.dmit@gmail.com \
--cc=users@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).