add the output of bootstrapbaserock/bootstrap-pass2baserock/bootstrap

2 files changed, 27 insertions, 0 deletions

diff --git a/gnulib b/gnulib
deleted file mode 160000
-Subproject 443bc5ffcf7429e557f4a371b0661abe98ddbc1
diff --git a/gnulib/doc/posix-functions/ctime.texi b/gnulib/doc/posix-functions/ctime.texi
new file mode 100644
index 0000000..6bff20c
--- /dev/null
+++ b/gnulib/doc/posix-functions/ctime.texi
@@ -0,0 +1,27 @@
+@node ctime
+@section @code{ctime}
+@findex ctime
+
+POSIX specification:@* @url{http://www.opengroup.org/onlinepubs/9699919799/functions/ctime.html}
+
+Gnulib module: ---
+
+Portability problems fixed by Gnulib:
+@itemize
+@end itemize
+
+Portability problems not fixed by Gnulib:
+@itemize
+@item
+This function may overflow its internal buffer if an invalid year is passed.
+@item
+The @code{ctime} function need not be reentrant, and consequently is
+not required to be thread safe.  Implementations of @code{ctime}
+typically write the time stamp into static buffer.  If two threads
+call @code{ctime} at roughly the same time, you might end up with the
+wrong date in one of the threads, or some undefined string.  There is
+a re-entrant interface @code{ctime_r}.
+@end itemize
+
+A more flexible function is @code{strftime}.  However, note that it is
+locale dependent.