From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1281] Build failure with Meson 1.2.1 on Windows
Date: Wed, 30 Aug 2023 16:35:19 +0000 [thread overview]
Message-ID: <bug-1281-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1281
Bug ID: 1281
Summary: Build failure with Meson 1.2.1 on Windows
Product: DPDK
Version: unspecified
Hardware: All
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
> meson.exe --werror -Dexamples=helloworld build
> ninja.exe -C build
[..]
[401/803] Compiling C object
lib/librte_eal.a.p/eal_x86_rte_power_intrinsics.c.obj
[402/803] Generating lib/rte_mempool_def with a custom command
[403/803] Compiling C object lib/librte_ring.a.p/ring_rte_ring.c.obj
[404/803] Linking static target lib/librte_ring.a
[405/803] Linking target lib/rte_eal-24.dll
FAILED: lib/rte_eal-24.dll
"clang" @lib/rte_eal-24.dll.rsp
clang: error: no such file or directory: 'librte_log.lib'
clang: error: no such file or directory: 'librte_kvargs.lib'
[406/803] Compiling C object
lib/librte_mempool.a.p/mempool_rte_mempool_ops_default.c.obj
[407/803] Compiling C object
lib/librte_mempool.a.p/mempool_mempool_trace_points.c.obj
[..]
OS: Windows Server 2019
Meson: 1.2.1 (Last known good version is 0.54.3)
Clang: 11.0.0 and 16.0.6
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3330 bytes --]
next reply other threads:[~2023-08-30 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 16:35 bugzilla [this message]
2023-10-07 6:38 ` [Bug 1281] Build failure with Meson 1.2.1 on Windows bugzilla
2023-10-09 7:35 ` 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-1281-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.