Richard Bos <[EMAIL PROTECTED]> writes:
> Is it possible to determine/get the block size that can be used by a
system? "block size" is too general a term. Your best bet is to
understand what the size is really being used for, and then look at a
low-level gnu package (I suggest coreutils) to see
The macros which compile a small C prog for testing a feature,
do they need the AC_PROG_CC macro to be called before?
/FAU
Richard Bos <[EMAIL PROTECTED]> writes:
> > configure already checks for fcntl.h, but how to check for the presence of
> > F_GETLK and or F_SETLK
Why not use "#ifdef F_GETLK"?
Richard Bos <[EMAIL PROTECTED]> writes:
> No one? No hint, advice or what so ever...?
Most all the code I've worked with assumes that fcntl locking is available
if fcntl is available. If you need to support pre-POSIX systems, you
should fall back on flock and lockf in that order, but these days
Frank A. Uepping wrote:
> I want to check for a kernel header file with AC_CHECK_HEADER.
Since you are wanting to use a kernel header file you should know that
you are leaving portable code behind and moving into the realm of only
running on a particular type of system. Of course a goal of autoco
Paul, Thamer and Russ thank you for providing your thoughts and tips about how
to deal with this issue.
Op zondag 3 augustus 2003 04:14, schreef Russ Allbery:
> Richard Bos <[EMAIL PROTECTED]> writes:
> > No one? No hint, advice or what so ever...?
>
> Most all the code I've worked with assumes
