From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Luca Boccassi <lboccass@brocade.com>
Cc: dev@dpdk.org, Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-dev] [PATCH] mk: add missing *CPPFLAGS to rte.compile-pre.mk
Date: Fri, 23 Sep 2016 18:24:17 +0200 [thread overview]
Message-ID: <3220422.mYu3b4OCfa@xps13> (raw)
In-Reply-To: <CAATJJ0JPEhzOTigcf=Lhvxi0FBwCWPQf6FUwb5r6Kkw+WyUM5A@mail.gmail.com>
2016-09-14 13:06, Christian Ehrhardt:
> On Tue, Aug 30, 2016 at 7:25 PM, Luca Boccassi <lboccass@brocade.com> wrote:
>
> > Some targets in mk/internal/rte.compile-pre.mk are calling CC or
> > HOSTCC without passing CPPFLAGS, EXTRA_CPPFLAGS or HOST_CPPFLAGS,
> > HOST_EXTRA_CPPFLAGS.
> > On Debian/Ubuntu builds this means that preprocessor flags set by the
> > dpkg-buildpackage environment, like hardening flags, are not
> > correctly passed to all objects builds.
> >
> > Signed-off-by: Luca Boccassi <lboccass@brocade.com>
> >
>
> Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Applied, thanks
prev parent reply other threads:[~2016-09-23 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 17:25 Luca Boccassi
2016-09-14 11:06 ` Christian Ehrhardt
2016-09-23 16:24 ` Thomas Monjalon [this message]
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=3220422.mYu3b4OCfa@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=lboccass@brocade.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 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).