All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1120] [19.11.13] drivers/raw/ifpga/base meson build error with gcc5.4 and clang3.8 on Ubuntu16.04
Date: Thu, 03 Nov 2022 01:40:05 +0000	[thread overview]
Message-ID: <bug-1120-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1120
           Summary: [19.11.13] drivers/raw/ifpga/base meson build error
                    with gcc5.4 and clang3.8 on Ubuntu16.04
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: daxuex.gao@intel.com
  Target Milestone: ---

Created attachment 230
  --> https://bugs.dpdk.org/attachment.cgi?id=230&action=edit
log

[git]
commit 104f5e8eb81e975809476fe894fc2781538ab752
Author: Luca Boccassi bluca@debian.org
Date:   Thu Aug 25 10:49:11 2022 +0100

    version: 19.11.13

    Signed-off-by: Luca Boccassi bluca@debian.org

[OS version]
 Ubuntu16.04.7LTS/4.4.0-186-generic
 GCC Version:     gcc 5.4.0 20160609
 Clang Version:    clang version 3.8.0

[Test setup]
CC=clang meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all
--default-library=static x86_64-native-linuxapp-clang
ninja -j 10 -C x86_64-native-linuxapp-clang

CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all
--default-library=static x86_64-native-linuxapp-gcc 
ninja -j 10 -C x86_64-native-linuxapp-gcc


[Error info]
please see the attachment.

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

                 reply	other threads:[~2022-11-03  1:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-1120-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.