[Freeciv-Dev] Re: (PR#4871) mingw32 build error in lockfile.c

["Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx>]

Per I. Mathisen wrote:
> gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../common    -O3
> -fomit-frame-pointer -Wall -Wpointer-arith -Wcast-align
> -Wmissing-prototypes -Wmissing-declarations -c `test -f 'lockfile.c' ||
> echo './'`lockfile.c
> lockfile.c: In function `create_lock':
> lockfile.c:77: variable `fl' has initializer but incomplete type
> lockfile.c:77: `F_WRLCK' undeclared (first use in this function)
> lockfile.c:77: (Each undeclared identifier is reported only once
> lockfile.c:77: for each function it appears in.)
> lockfile.c:77: warning: excess elements in struct initializer
> lockfile.c:77: warning: (near initialization for `fl')
> lockfile.c:77: warning: excess elements in struct initializer
> lockfile.c:77: warning: (near initialization for `fl')
> lockfile.c:77: warning: excess elements in struct initializer
> lockfile.c:77: warning: (near initialization for `fl')
> lockfile.c:77: warning: excess elements in struct initializer
> lockfile.c:77: warning: (near initialization for `fl')
> lockfile.c:77: warning: excess elements in struct initializer
> lockfile.c:77: warning: (near initialization for `fl')
> lockfile.c:77: storage size of `fl' isn't known
> lockfile.c:91: warning: implicit declaration of function `fcntl'
> lockfile.c:91: `F_SETLK' undeclared (first use in this function)
> lockfile.c:77: warning: unused variable `fl'
> lockfile.c: In function `remove_lock':
> lockfile.c:114: variable `fl' has initializer but incomplete type
> lockfile.c:114: `F_UNLCK' undeclared (first use in this function)
> lockfile.c:114: warning: excess elements in struct initializer
> lockfile.c:114: warning: (near initialization for `fl')
> lockfile.c:114: warning: excess elements in struct initializer
> lockfile.c:114: warning: (near initialization for `fl')
> 
> And so on. Please advise.

What header files (if any) define F_WRLCK and the other values?  Can we 
add a configure-time test for these files and a (protected) #inclusion 
within lockfile.c?

jason