From 8804f5bdd7cbc0bc8166c7a4a9a09fbcb4402afd Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 20 Dec 2007 10:33:13 +0100 Subject: Attempt to fix the build James, at least on my Linux system neither FILE_CASE_SENSITIVE_SEARCH nor FILE_CASE_PRESERVING_NAMES seem to be defined anywhere. Is it possible that this is a MacOS/X specific thing? If so, could you add configure tests for this? Thanks, Volker (This used to be commit 465fd4385013c95f9778d710d70796feae4eb858) --- source3/smbd/statvfs.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'source3/smbd/statvfs.c') diff --git a/source3/smbd/statvfs.c b/source3/smbd/statvfs.c index 5fc0afdd79..431489032c 100644 --- a/source3/smbd/statvfs.c +++ b/source3/smbd/statvfs.c @@ -39,11 +39,13 @@ static int linux_statvfs(const char *path, vfs_statvfs_struct *statbuf) statbuf->FreeFileNodes = statvfs_buf.f_ffree; statbuf->FsIdentifier = statvfs_buf.f_fsid; +#if defined(FILE_CASE_SENSITIVE_SEARCH) && defined(FILE_CASE_PRESERVING_NAMES) /* Good defaults for Linux filesystems are case sensitive * and case preserving. */ statbuf->FsCapabilities = FILE_CASE_SENSITIVE_SEARCH | FILE_CASE_PRESERVING_NAMES; +#endif } return result; } -- cgit