Take care: thread-safety does not imply that you can have multiple callers -access and close the same file. There is no resource tracking to that degree -yet. All that the thread-safety tries to afford you is not to get into big trouble -if simultaneous and overlapping accesses to files, memory allocation and other -resources are taking place.
- -Also take care with file I/O involving the stdin/stdout/stderr -streams; read/write operations on these streams will be mapped to the Input()/Output()/ErrorOutput() -file handles of the process performing these operations. Since only this small set of -operations is mapped, functions such as fcntl() or select() will not -work on the stdin/stdout/stderr streams and the corresponding -file descriptors STDIN_FILENO/STDOUT_FILENO/STDERR_FILENO. -It is therefore strongly recommended to use the thread-safe library only for applications -which can cope with the limitations described above.
-The plain libc.a, which your software would be linked against by default, does not contain +any floating point support code. This means, for example, that printf("%f",...) will not produce +the desired output and that scanf("%f",...) may not read any data at all. If your +program needs functions such as these or atod() then you must link against libm.a or +the equivalent.
+ +To link the floating point support code with your software, use the -lm compiler option. Careful! +The order in which you specify the libraries to link against is important here. Thus, gcc -o test test.c -lm -lc +would correctly link the program test against the proper floating point math library, but +gcc -o test test.c -lc -lm would not.
+ +Thread-safety does not imply that you can have multiple callers +access and close the same file. There is no resource tracking to that degree +yet. All that the thread-safety tries to afford you is not to get into big trouble +if simultaneous and overlapping accesses to files, memory allocation and other +resources are taking place.
+ +Also take care with file I/O involving the stdin/stdout/stderr +streams; read/write operations on these streams will be mapped to the Input()/Output()/ErrorOutput() +file handles of the process performing these operations. Since only this small set of +operations is mapped, functions such as fcntl() or select() will not +work on the stdin/stdout/stderr streams and the corresponding +file descriptors STDIN_FILENO/STDOUT_FILENO/STDERR_FILENO. +It is therefore strongly recommended to use the thread-safe library only for applications +which can cope with the limitations described above.
+ +