All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36
Date: Thu, 12 May 2022 08:40:52 +0000	[thread overview]
Message-ID: <bug-1008-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=1008

            Bug ID: 1008
           Summary: Building DPDK with gcc 12.1.1 throws warnings on
                    Fedora 36
           Product: DPDK
           Version: 21.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: krzysztof.karas@intel.com
  Target Milestone: ---

Created attachment 202
  --> https://bugs.dpdk.org/attachment.cgi?id=202&action=edit
zip archive with build logs in txt format

I use a Vagrant box with Fedora 36, gcc 12.1.1 installed and encountered
multiple warnings during compliation. I have tried to build the project
(version 21.11.1) in two ways:

meson build; ninja -C build

and

meson --buildtype=debug build; ninja -C build

Warnings generated in both cases differ. I have attached the build logs (2 for
meson and 2 for ninja build) as text files (zipped).

Version of my OS:
[vagrant@fedora36-cloud-25983 ~]$ uname -a
Linux fedora36-cloud-25983 5.17.2-300.fc36.x86_64 #1 SMP PREEMPT Fri Apr 8
14:35:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2022-05-12  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  8:40 bugzilla [this message]
2022-06-15  8:46 ` [Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36 bugzilla

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=bug-1008-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.