MySQL Bugs: #7764: InnoDB compile failure: `F

Bug #7764	InnoDB compile failure: `F_FULLFSYNC' undeclared
Submitted:	10 Jan 2005 11:37	Modified:	10 Jan 2005 14:04
Reporter:	Lenz Grimmer	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	4.1.9-pre	OS:	MacOS (Mac OS X 10.2.x)
Assigned to:	Heikki Tuuri	CPU Architecture:	Any

Description:
Compiling InnoDB currently fails on Mac OS X 10.2.x (but NOT on 10.3.x!) with the following error:

[SNIP]
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./../include -I./../../include -I../../include    -DDBUG_OFF -O -DDBUG_OFF -O3 -fno-omit-frame-pointer -DHAVE_DARWIN_THREADS -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ -DHAVE_BROKEN_REALPATH  -DDEBUG_OFF -MT os0file.o -MD -MP -MF ".deps/os0file.Tpo" -c -o os0file.o os0file.c; \
then mv -f ".deps/os0file.Tpo" ".deps/os0file.Po"; else rm -f ".deps/os0file.Tpo"; exit 1; fi
os0file.c: In function `os_file_flush':
os0file.c:1772: error: `F_FULLFSYNC' undeclared (first use in this function)
os0file.c:1772: error: (Each undeclared identifier is reported only once
os0file.c:1772: error: for each function it appears in.)
make[4]: *** [os0file.o] Error 1
[SNIP]

Seems like F_FULLFSYNC was not implemented in Mac OS X 10.2.x yet?

How to repeat:
Compile the current 4.1 tree on Mac OS X 10.2.x, observe the compile error.

Fixed and pushed to the current 4.1 tree.

We simply use fsync() if F_FULLFSYNC is undefined.

--Heikki