From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/trace-cmd: bump to version 2.3.2
Date: Sun, 8 Jun 2014 15:22:43 +0200 [thread overview]
Message-ID: <20140608152243.48fd5c25@free-electrons.com> (raw)
In-Reply-To: <1402006038-8840-2-git-send-email-romain.naour@openwide.fr>
Dear Romain Naour,
On Fri, 6 Jun 2014 00:07:18 +0200, Romain Naour wrote:
> The first patch "use-pkg-config-instead-of-python-config" has been applied upstream.
>
> The flag _GNU_SOURCE is now always defined in Makefile, so it can be removed from trace-cmd.mk
>
> CPPFLAGS are appended to CFLAGS and are used to add extra flags, but the flag _LARGEFILE64_SOURCE
> in TARGET_CPPFLAGS is already defined in source files, which causes a build error.
> CPPFLAGS are cleared before passing them to the trace-cmd Makefile.
Please wrap your commit message properly.
> # trace-cmd already defines _LARGEFILE64_SOURCE when necessary,
> # redefining it on the command line causes build problems.
> -TRACE_CMD_CFLAGS = $(filter-out -D_LARGEFILE64_SOURCE,$(TARGET_CFLAGS)) -D_GNU_SOURCE
> +TRACE_CMD_CFLAGS = $(filter-out -D_LARGEFILE64_SOURCE,$(TARGET_CFLAGS))
> +
> +# trace-cmd use CPPFLAGS to add some extra flags.
> +# But like for CFLAGS, $(TARGET_CPPFLAGS) contains _LARGEFILE64_SOURCE
> +# that causes build problems.
> +TRACE_CMD_CPPFLAGS = ""
And therefore why don't you use the same strategy as the one used for
CFLAGS, by filtering out the -D_LARGEFILE64_SOURCE ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-08 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 22:07 [Buildroot] [PATCH 1/2] package/trace-cmd: update download url Romain Naour
2014-06-05 22:07 ` [Buildroot] [PATCH 2/2] package/trace-cmd: bump to version 2.3.2 Romain Naour
2014-06-08 13:22 ` Thomas Petazzoni [this message]
2014-06-08 16:40 ` Romain Naour
2014-06-08 13:21 ` [Buildroot] [PATCH 1/2] package/trace-cmd: update download url Thomas Petazzoni
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=20140608152243.48fd5c25@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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