mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-02-23 18:52:09 +01:00
7589569f13
1998-12-11 Sebastian Wilhelmi <wilhelmi@ira.uka.de> * gthread/gthread-nspr.c, configure.in: Added new default thread implementation on top of the mozilla nspr library. * gmem.c, gmessaged.c, gthread/gthread.c, gthread/gthread-*.c: Changed GStaticMutex and GStaticPrivate in gmem.c and gmessages.c into GMutex and GPrivate resp. to make error reporting and use of gmem possible in most (not all, though) gthread functions. Also initialized the modules via new init functions. * configure.in: Fixed syntax bug in definition of type GStaticMutex. * gthread/testgthread.c: Updated to work with nspr, but see note there for remaining problems.
General Information =================== This is GLib version 1.1.6. GLib, is a library which includes support routines for C such as lists, trees, hashes, memory allocation, and many other things. Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior to 1.1.0. The official ftp site is: ftp://ftp.gtk.org/pub/gtk The official web site is: http://www.gtk.org/ A mailing list is located at: gtk-list@redhat.com To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null (Send mail to gtk-list-request@redhat.com with the subject "subscribe") Installation ============ See the file 'INSTALL' How to report bugs ================== To report a bug, send mail either to gtk-list, as mentioned above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you must be subscribed yourself. In the mail include: * The version of GLib * Information about your system. For instance: - What operating system and version - What version of X - For Linux, what version of the C library And anything else you think is relevant. * How to reproduce the bug. If you can reproduce it with the testglib program that is built in the glib/ directory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded. * If the bug was a crash, the exact text that was printed out when the crash occured. * Further information such as stack traces may be useful, but is not necessary. Patches ======= Patches can be uploaded to the incoming/ directory on ftp.gtk.org. Please follow the instructions there, and include your name and email address in the README file. If the patch fixes a bug, it is usually a good idea to include all the information described in "How to Report Bugs".