Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] lttng-tools: fix build on uClibc due to sync_file_range()
Date: Sun, 05 Feb 2012 11:11:09 +0100	[thread overview]
Message-ID: <87pqdtsi82.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <cd91ba13b014d9e86a017ab35858badd0a4b69cb.1328366921.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sat, 4 Feb 2012 15:48:43 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Add a patch to use fdatasync() instead of sync_file_range() when the
 Thomas> latter is not available.

 Thomas> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 Thomas> ---
 Thomas>  ...ls-2.0-pre15-no-sync-file-range-in-uclibc.patch |   87 ++++++++++++++++++++
 Thomas>  package/lttng-tools/lttng-tools.mk                 |    2 +
 Thomas>  2 files changed, 89 insertions(+), 0 deletions(-)
 Thomas>  create mode 100644 package/lttng-tools/lttng-tools-2.0-pre15-no-sync-file-range-in-uclibc.patch

 Thomas> diff --git a/package/lttng-tools/lttng-tools-2.0-pre15-no-sync-file-range-in-uclibc.patch b/package/lttng-tools/lttng-tools-2.0-pre15-no-sync-file-range-in-uclibc.patch
 Thomas> new file mode 100644
 Thomas> index 0000000..861686b
 Thomas> --- /dev/null
 Thomas> +++ b/package/lttng-tools/lttng-tools-2.0-pre15-no-sync-file-range-in-uclibc.patch
 Thomas> @@ -0,0 +1,87 @@
 Thomas> +Make sync_file_range() usage optional
 Thomas> +
 Thomas> +Under uClibc, sync_file_range() is not available under all
 Thomas> +architectures, so we fall back to fdatasync() in this case.

And as far as I can see, it's also only available if LFS support is
present.

Committed, thanks. Don't forget to send patch upstream.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-02-05 10:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 14:48 [Buildroot] [pull request] Pull request for branch for-2012.02/lttng-uclibc-fixes Thomas Petazzoni
2012-02-04 14:48 ` [Buildroot] [PATCH 1/7] liburcu: add patch to fix build with uClibc Thomas Petazzoni
2012-02-05 10:00   ` Peter Korsgaard
2012-02-05 10:07     ` Thomas Petazzoni
2012-02-04 14:48 ` [Buildroot] [PATCH 2/7] lttng-tools: fix build on uClibc due to sync_file_range() Thomas Petazzoni
2012-02-05 10:11   ` Peter Korsgaard [this message]
2012-02-04 14:48 ` [Buildroot] [PATCH 3/7] lttng-babeltrace: make sure WCHAR and LARGEFILE are enabled Thomas Petazzoni
2012-02-05 10:15   ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 4/7] lttng-libust: add the dependency on util-linux Thomas Petazzoni
2012-02-05 10:15   ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 5/7] lttng-tools: make the dependency on lttng-libust optional Thomas Petazzoni
2012-02-05 10:17   ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 6/7] lttng-libust: add patch to fix build issue when C++ support is not available Thomas Petazzoni
2012-02-05 10:28   ` Peter Korsgaard
2012-02-04 14:48 ` [Buildroot] [PATCH 7/7] lttng-babeltrace: fix build on uClibc due to missing posix_fallocate() Thomas Petazzoni
2012-02-05 13:41   ` Peter Korsgaard

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=87pqdtsi82.fsf@macbook.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