[Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36

[Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36

[bugzilla]

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.

[Bug 1008] Building DPDK with gcc 12.1.1 throws warnings on Fedora 36

[bugzilla]

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

David Marchand (david.marchand@redhat.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
                 CC|                            |david.marchand@redhat.com
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from David Marchand (david.marchand@redhat.com) ---
Thanks, there were several other reports for the various issues, I prefer to
close this one. Feel free to open a bugzilla for any remaining issue that has
no assigned bz.

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