From 59c8e4de91bb0499be741252fc4f6ec10d7dc5b0 Mon Sep 17 00:00:00 2001 From: Peter Korsgaard Date: Sat, 3 Oct 2009 22:15:04 +0200 Subject: valgrind: fix build without largefile support Signed-off-by: Peter Korsgaard --- package/valgrind/valgrind-largefile.patch | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 package/valgrind/valgrind-largefile.patch (limited to 'package/valgrind') diff --git a/package/valgrind/valgrind-largefile.patch b/package/valgrind/valgrind-largefile.patch new file mode 100644 index 000000000..9ef5708bc --- /dev/null +++ b/package/valgrind/valgrind-largefile.patch @@ -0,0 +1,27 @@ +[PATCH] valgrind: don't enable largefile support unconditionally on uClibc + +uClibc can be compiled without largefile support (and errors out if +_FILE_OFFSET_BITS is set to 64), so don't define it if that combination +is detected. + +Signed-off-by: Peter Korsgaard +--- + coregrind/m_ume.c | 4 ++++ + 1 file changed, 4 insertions(+) + +Index: valgrind-3.2.3/coregrind/m_ume.c +=================================================================== +--- valgrind-3.2.3.orig/coregrind/m_ume.c ++++ valgrind-3.2.3/coregrind/m_ume.c +@@ -31,7 +31,11 @@ + + + #define _GNU_SOURCE ++#include ++/* uclibc without largefile support #errors on _FILE_OFFSET_BITS=64 */ ++#if !(defined(__UCLIBC__) && !defined(__UCLIBC_HAS_LFS__)) + #define _FILE_OFFSET_BITS 64 ++#endif + + // It seems that on SuSE 9.1 (x86) something in messes up stuff + // acquired indirectly from vki-x86-linux.h. Therefore our headers must be -- cgit v1.2.3