Lines Matching refs:OS
48 ** underlying operating system supports it. If the OS lacks
49 ** large file support, or if the OS is windows, these should be no-ops.
63 ** Similar is true for Mac OS X. LFS is only supported on Mac OS X 9 and later.
404 ** recursive mutexes on most Unix systems. But Mac OS X is different.
405 ** The _XOPEN_SOURCE define causes problems for Mac OS X we are told,
900 #define SQLITE_NOLFS 22 /* Uses OS features not supported on host */
1033 ** to use Mac OS X style fullsync instead of fsync().
1040 ** CAPI3REF: OS Interface Open File Handle
1043 ** [sqlite3_vfs | OS interface layer]. Individual OS interface
1056 ** CAPI3REF: OS Interface File Virtual Methods Object
1072 ** The second choice is a Mac OS X style fullsync. The [SQLITE_SYNC_DATAONLY]
1193 ** CAPI3REF: OS Interface Object
1429 ** are built into SQLite when it is compiled for Unix, Windows, or OS/2.
2344 ** The Windows OS interface layer calls
5157 ** are appropriate for use on OS/2, Unix, and Windows.
7814 /************** Include os.h in the middle of sqliteInt.h ********************/
7815 /************** Begin file os.h **********************************************/
7829 ** "os.c") attempt to abstract the underlying operating system so that
7935 ** OS's standard temporary file directory, and are deleted prior to exit.
8041 ** Wrapper around OS specific sqlite3_os_init() function.
8088 /************** End of os.h **************************************************/
8131 ** SQLITE_MUTEX_OS2 For multi-threaded applications on OS/2.
8310 sqlite3_vfs *pVfs; /* OS Interface */
12046 /************** Begin file os.c **********************************************/
12059 ** This file contains OS interface code that is common to all
12242 ** This function is a wrapper around the OS specific implementation of
12344 /************** End of os.c **************************************************/
14738 ** This file contains the C functions that implement mutexes for OS/2
14747 /********************** OS/2 Mutex Implementation **********************
14749 ** This implementation of mutexes is built using the OS/2 API.
16371 ** faster than the library printf for SUN OS 4.1.
19955 ** This file contains code that is specific to OS/2.
19967 ** malloc failures happen frequently. OS/2 does not typically run on
19976 ** the OS driver, but the code to deal with those failure would not
19982 ** OS layer for an embedded system, if you use this file as an example,
19983 ** avoid the use of malloc()/free(). Those routines work ok on OS/2
20219 ** The os2File structure is subclass of sqlite3_file specific for the OS/2
20450 APIRET res = NO_ERROR; /* Result of an OS/2 lock call */
20545 OSTRACE2( "OS/2 error-code = %d\n", res );
20747 ** Helper function to convert UTF-8 filenames to local OS/2 codepage.
21375 ** underlying operating system supports it. If the OS lacks
22230 ** tid is omitted if we compile without threading support or on an OS
22487 /* On OS X on an msdos filesystem, the inode number is reported
22489 ** around this problem (we consider it a bug in OS X, not SQLite)
22760 ** Symbols defined in os.h indentify the 'pending byte' and the 'reserved
23106 ** OS call only when all threads in this same process have released
24441 ** only available on Mac OS X. But that could change.
24458 ** enabled, however, since with SQLITE_NO_SYNC enabled, an OS crash
24654 ** in the OS-X msdos filesystem. In order to avoid problems with upper
25336 ** Previously, the SQLite OS layer used three functions in place of this
25894 ** cache exposes a cache coherency problem that is present on all OS X
27127 ** the OS driver, but the code to deal with those failure would not
27133 ** OS layer for an embedded system, if you use this file as an example,
28637 void *zConverted; /* Filename in OS encoding */
29171 ** strerror_r() on unix). After an error is returned by an OS
29173 ** a buffer of nBuf bytes. The OS layer should populate the
31672 sqlite3_vfs *pVfs; /* OS functions to use for IO */
32243 ** that will be implicitly filled in by the OS).
33616 ** Adjust the robustness of the database to damage due to OS crashes
33663 ** or some other error code if we fail. The OS will automatically
33956 /* The OS lock values must be the same as the Pager lock values */
39830 ** how well the database resists damage due to OS crashes and power
41225 ** (when less compiler optimizations like -Os or -O0 are used and the
51169 ** switches (-Os), gcc may align this Mem object on a 4-byte boundary
