All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1245] Windows build failure with clang (unresolved external symbol)
Date: Thu, 08 Jun 2023 06:34:26 +0000	[thread overview]
Message-ID: <bug-1245-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

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

            Bug ID: 1245
           Summary: Windows build failure with clang (unresolved external
                    symbol)
           Product: DPDK
           Version: 23.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

> meson.exe --werror -Dexamples=helloworld build
> ninja.exe -C build
[..]
[577/818] Linking target drivers/rte_bus_pci-23.dll
FAILED: drivers/rte_bus_pci-23.dll
clang @drivers/rte_bus_pci-23.dll.rsp
rte_bus_pci_exports.def : error LNK2001: unresolved external symbol
rte_pci_mmio_read
rte_bus_pci_exports.def : error LNK2001: unresolved external symbol
rte_pci_mmio_write
drivers\rte_bus_pci.lib : fatal error LNK1120: 2 unresolved externals
clang: error: linker command failed with exit code 1120 (use -v to see
invocation)
[..]

Git bisect points to 095cf6e68b28 ("bus/pci: introduce MMIO read/write")

Meson: 0.54.3
Clang: 11.0.0
Clang link: 14.28.29335.0

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

[-- Attachment #2: Type: text/html, Size: 3169 bytes --]

             reply	other threads:[~2023-06-08  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  6:34 bugzilla [this message]
2023-06-12 20:55 ` [Bug 1245] Windows build failure with clang (unresolved external symbol) 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-1245-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.