From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] trace-cmd: fix largefile build problem
Date: Tue, 01 Oct 2013 23:29:06 +0200 [thread overview]
Message-ID: <8738oku1ct.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1380576047-21001-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Mon, 30 Sep 2013 23:20:44 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> The source files of trace-cmd already define _LARGEFILE64_SOURCE, but
Thomas> Buildroot passes it again on the build command line through CFLAGS,
Thomas> which causes a build error. We fix this by filtering out our
Thomas> definition of _LARGEFILE64_SOURCE from the CFLAGS before passing them
Thomas> to the trace-cmd Makefile.
Thomas> Fixes the warning visible at:
Thomas> http://autobuild.buildroot.net/results/1c4567a230940a5287d03e2a5c2c7afbdc64cd36/build-end.log
It's just a warning, but ok - Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-10-01 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 21:20 [Buildroot] [PATCH 1/4] trace-cmd: fix largefile build problem Thomas Petazzoni
2013-09-30 21:20 ` [Buildroot] [PATCH 2/4] python: fix python-config for cross-compilation Thomas Petazzoni
2013-10-01 21:58 ` Peter Korsgaard
2013-10-02 7:13 ` Thomas Petazzoni
2013-10-02 7:43 ` Peter Korsgaard
2013-09-30 21:20 ` [Buildroot] [PATCH 3/4] python3: " Thomas Petazzoni
2013-09-30 21:20 ` [Buildroot] [PATCH 4/4] trace-cmd: improve Python support Thomas Petazzoni
2013-10-01 21:29 ` Peter Korsgaard [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=8738oku1ct.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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