From: Tal Shnaiderman <talshn@nvidia.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
"dmitrym@microsoft.com" <dmitrym@microsoft.com>,
"navasile@linux.microsoft.com" <navasile@linux.microsoft.com>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>,
"Nick Connolly" <nick.connolly@mayadata.io>,
"John.Alexander@datapath.co.uk" <John.Alexander@datapath.co.uk>,
Khoa To <khot@microsoft.com>, "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"Ali Alnubani" <alialnu@nvidia.com>, Odi Assli <odia@nvidia.com>
Subject: Re: [dpdk-dev] Windows build broken on latest meson/ninja release
Date: Wed, 6 Jan 2021 15:53:58 +0000 [thread overview]
Message-ID: <DM6PR12MB3945C8311364EC044A0D8302A4D00@DM6PR12MB3945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210106152214.GC1969@bricha3-MOBL.ger.corp.intel.com>
> Subject: Re: [dpdk-dev] Windows build broken on latest meson/ninja release
>
> External email: Use caution opening links or attachments
>
>
> On Wed, Jan 06, 2021 at 03:18:17PM +0000, Tal Shnaiderman wrote:
> > Hi,
> >
> > We're testing Windows build with the latest meson/ninja version
> > available in the meson github [1]
> >
> > meson: 0.56.0
> > ninja: 1.10.2
> >
> > and getting the output below, any idea why? looks like a bug since
> /subsystem should be recognized.
> >
> > FAILED: examples/dpdk-helloworld.exe examples/dpdk-helloworld.pdb
> > "clang" -Wl,/MACHINE:X64 -Wl,/OUT:examples/dpdk-helloworld.exe
> examples/dpdk-helloworld.exe.p/helloworld_main.c.obj "-Wl,/nologo" "-
> Wl,/release" "-Wl,/nologo" "-Wl,/DEBUG" "-Wl,/PDB:examples\dpdk-
> helloworld.pdb" "-Wl,/WHOLEARCHIVE:lib\librte_hash.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_cmdline.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_pci.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_ethdev.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_meter.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_net.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_mbuf.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_mempool.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_rcu.a" "-Wl,/WHOLEARCHIVE:lib\librte_ring.a"
> "-Wl,/WHOLEARCHIVE:lib\librte_eal.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_telemetry.a" "-
> Wl,/WHOLEARCHIVE:lib\librte_kvargs.a" "-
> Wl,/WHOLEARCHIVE:drivers\librte_bus_pci.a" "-
> Wl,/WHOLEARCHIVE:drivers\librte_bus_vdev.a" "-
> Wl,/WHOLEARCHIVE:drivers\librte_mempool_ring.a" "-lws2_32" "-lmincore"
> "-ladvapi32" "-lsetupapi" "-ldbghelp" "-g" "lib\librte_hash.a"
> "lib\librte_cmdline.a" "lib\librte_pci.a" "lib\librte_ethdev.a"
> "lib\librte_meter.a" "lib\librte_net.a" "lib\librte_mbuf.a"
> "lib\librte_mempool.a" "lib\librte_rcu.a" "lib\librte_ring.a" "lib\librte_eal.a"
> "lib\librte_telemetry.a" "lib\librte_kvargs.a" "drivers\librte_bus_pci.a"
> "drivers\librte_bus_vdev.a" "drivers\librte_mempool_ring.a" "-Wl,--
> subsystem,console" "-lkernel32" "-luser32" "-lgdi32" "-lwinspool" "-lshell32"
> "-lole32" "-loleaut32" "-luuid" "-lcomdlg32"
> > LINK : warning LNK4044: unrecognized option '/-subsystem'; ignored
> > LINK : fatal error LNK1181: cannot open input file 'console.obj'
> > clang: error: linker command failed with exit code 1181 (use -v to see
> > invocation) [165/190] Linking target examples/dpdk-l2fwd.exe
> > FAILED: examples/dpdk-l2fwd.exe examples/dpdk-l2fwd.pdb
> >
> > [1] -
> >
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> >
> ub.com%2Fmesonbuild%2Fmeson%2Freleases&data=04%7C01%7Ctals
> hn%40nvi
> >
> dia.com%7C018f5de217d74c7789a708d8b256e245%7C43083d15727340c1b7db
> 39efd
> >
> 9ccc17a%7C0%7C0%7C637455433541219307%7CUnknown%7CTWFpbGZsb3d
> 8eyJWIjoiM
> >
> C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000
> &s
> >
> data=n1RAieccH6hTWFk7o9B68bysK8BFi6hvnsHdwsjAghA%3D&reserve
> d=0
> >
>
> Maybe one better asked of the meson community?
> Does the "-Wl,--subsystem,console" come from our meson.build files, or
> from meson itself?
It's a good idea, especially since this is not the first time meson upgrades broke DPDK (at least for Windows).
I think is this meson itself, I don't remember seeing this set explicitly in the build files.
next prev parent reply other threads:[~2021-01-06 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:18 Tal Shnaiderman
2021-01-06 15:22 ` Bruce Richardson
2021-01-06 15:53 ` Tal Shnaiderman [this message]
2021-01-06 15:23 ` David Marchand
2021-01-06 15:59 ` Tal Shnaiderman
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=DM6PR12MB3945C8311364EC044A0D8302A4D00@DM6PR12MB3945.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=John.Alexander@datapath.co.uk \
--cc=alialnu@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=khot@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=nick.connolly@mayadata.io \
--cc=odia@nvidia.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).