All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dmitry.kozliuk@gmail.com
Cc: dev@dpdk.org, Jeremy Plsek <jplsek@iol.unh.edu>,
	pallavi.kadam@intel.com, ranjit.menon@intel.com,
	harini.ramakrishnan@microsoft.com,
	Tal Shnaiderman <talshn@mellanox.com>
Subject: Re: [dpdk-dev] DPDK Windows Build
Date: Tue, 04 Feb 2020 22:51:20 +0100	[thread overview]
Message-ID: <3336093.R56niFO833@xps> (raw)
In-Reply-To: <20c66c3e-35ee-9433-467d-6d72cd336149@iol.unh.edu>

29/01/2020 19:05, Jeremy Plsek:
> Hi Dmitry,
> 
> > There is a bug in Meson: '/OPT:REF' must be prefixed with '-Wl,' when using
> > Clang with link.exe, because Clang does not recognize '/OPT:REF' as an
> > argument to pass to linker, but treats it as a filename instead.
> > A patch is not under review: https://github.com/mesonbuild/meson/pull/6483
> 
> Thanks for the suggestion. I applied the patch to meson and the OPT 
> error is gone and it now compiles.
> 
> Thanks!

Wonderful, thanks Dmitry for the patch in meson.

Please would you like to add a note with a link to the patch in the DPDK doc?



  parent reply	other threads:[~2020-02-04 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 18:05 [dpdk-dev] DPDK Windows Build Jeremy Plsek
     [not found] ` <CALDO+SbTP6jsAsPyupHsXy2+qJLg5ndu31GLniQJN84=be2bNg@mail.gmail.com>
2020-02-01 11:43   ` Dmitry Kozliuk
2020-02-03 19:26     ` William Tu
2020-02-03 22:08       ` Dmitry Kozlyuk
2020-02-03 22:25         ` William Tu
2020-02-03 23:02           ` Dmitry Kozlyuk
2020-02-03 23:26             ` William Tu
2020-02-03 23:43               ` Dmitry Kozliuk
2020-02-04  0:55                 ` William Tu
2020-02-04  6:16                   ` Dmitry Kozlyuk
2020-02-04 20:58                     ` William Tu
2020-02-04 21:51 ` Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-28 16:42 Jeremy Plsek
2020-01-28 21:36 ` Dmitry Kozliuk

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=3336093.R56niFO833@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=jplsek@iol.unh.edu \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=talshn@mellanox.com \
    /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.