From 35911ae00f5348ea4a60d66db25d70a1c45c9c43 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Fri, 26 Jun 2009 23:09:35 -0400 Subject: [PATCH] Fix a typo --- docs/reference/glib/building.sgml | 84 +++++++++++++++++++-------------------- 1 file changed, 42 insertions(+), 42 deletions(-) diff --git a/docs/reference/glib/building.sgml b/docs/reference/glib/building.sgml index 72c82b3..b28ed53 100644 --- a/docs/reference/glib/building.sgml +++ b/docs/reference/glib/building.sgml @@ -40,9 +40,9 @@ How to compile GLib itself the standard options. - The GTK+ documentation contains - further details - about the build process and ways to influence it. + The GTK+ documentation contains + further details + about the build process and ways to influence it. @@ -62,11 +62,11 @@ How to compile GLib itself url="http://www.freedesktop.org/software/pkgconfig/">pkg-config is a tool for tracking the compilation flags needed for libraries that are used by the GLib library. (For each - library, a small .pc text file is - installed in a standard location that contains the compilation - flags needed for that library along with version number - information.) The version of pkg-config - needed to build GLib is mirrored in the + library, a small .pc text file is + installed in a standard location that contains the compilation + flags needed for that library along with version number + information.) The version of pkg-config + needed to build GLib is mirrored in the dependencies directory on the GTK+ FTP site. @@ -95,27 +95,27 @@ How to compile GLib itself system doesn't have the iconv() function for doing conversion between character encodings. Most modern systems should have - iconv(), however many older systems lack - an iconv() implementation. On such systems, + iconv(), however many older systems lack + an iconv() implementation. On such systems, you must install the libiconv library. This can be found at: - http://www.gnu.org/software/libiconv. + http://www.gnu.org/software/libiconv. If your system has an iconv() implementation but you want to use libiconv instead, you can pass the --with-libiconv option to configure. This forces - libiconv to be used. + libiconv to be used. Note that if you have libiconv installed in your default include search path (for instance, in /usr/local/), but don't enable it, you will get an error while compiling GLib because the iconv.h that libiconv installs hides the - system iconv. + system iconv. If you are using the native iconv implementation on Solaris - instead of libiconv, you'll need to make sure that you have + instead of libiconv, you'll need to make sure that you have the converters between locale encodings and UTF-8 installed. At a minimum you'll need the SUNWuiu8 package. You probably should also install the SUNWciu8, SUNWhiu8, SUNWjiu8, and @@ -143,7 +143,7 @@ How to compile GLib itself A thread implementation is needed, unless you want to compile GLib without thread support, which is not recommended. The thread support in GLib can be based upon several native thread implementations, - e.g. POSIX threads, DCE threads or Solaris threads. + e.g. POSIX threads, DCE threads or Solaris threads. @@ -158,17 +158,17 @@ How to compile GLib itself - The optional extended attribute support in GIO requires the - getxattr() family of functions that may be provided by glibc or - by the standalone libattr library. To build GLib without extended - attribute support, use the + The optional extended attribute support in GIO requires the + getxattr() family of functions that may be provided by glibc or + by the standalone libattr library. To build GLib without extended + attribute support, use the configure option. - The optional SELinux support in GIO requires libselinux. To build - GLib without SELinux support, use the + The optional SELinux support in GIO requires libselinux. To build + GLib without SELinux support, use the configure option. @@ -289,7 +289,7 @@ How to compile GLib itself - When growing a GArray, Glib will clear the new chunk of memory. + When growing a GArray, Glib will clear the new chunk of memory. Grow an array from 7 bytes to 10 bytes, and the last 3 bytes will be cleared. @@ -301,7 +301,7 @@ How to compile GLib itself When freeing a node from a GHashTable, Glib will first clear - the node, which used to have pointers to the key and the value + the node, which used to have pointers to the key and the value stored at that node. @@ -328,16 +328,16 @@ How to compile GLib itself For sparse memory systems this behaviour is often inferior, so memory pools can be disabled to avoid excessive caching and force atomic maintenance of chunks through the g_malloc() - and g_free() functions. Code currently affected by + and g_free() functions. Code currently affected by this: GList, GSList, - GNode, GHash - allocations. The functions g_list_push_allocator(), - g_list_pop_allocator(), g_slist_push_allocator(), - g_slist_pop_allocator(), g_node_push_allocator() and + GNode, GHash + allocations. The functions g_list_push_allocator(), + g_list_pop_allocator(), g_slist_push_allocator(), + g_slist_pop_allocator(), g_node_push_allocator() and g_node_pop_allocator() are not available @@ -348,20 +348,20 @@ How to compile GLib itself - GSignal disables all caching (potentially + GSignal disables all caching (potentially very slow) - GType doesn't honour the - GTypeInfo + GType doesn't honour the + GTypeInfo n_preallocs field anymore - the GBSearchArray flag + the GBSearchArray flag G_BSEARCH_ALIGN_POWER2 becomes non-functional @@ -467,12 +467,12 @@ How to compile GLib itself By default the configure script will try to auto-detect whether the C library provides a suitable set - of printf() functions. In detail, + of printf() functions. In detail, configure checks that the semantics of snprintf() are as specified by C99 and that positional parameters as specified in the Single Unix Specification are supported. If this not the case, GLib will - include an implementation of the printf() + include an implementation of the printf() family. These options can be used to explicitly control whether an implementation fo the printf() family @@ -488,11 +488,11 @@ How to compile GLib itself By default, GLib uses ELF visibility attributes to optimize PLT table entries if the compiler supports ELF visibility attributes. A side-effect of the way in which this is currently - implemented is that any header change forces a full - recompilation, and missing includes may go unnoticed. + implemented is that any header change forces a full + recompilation, and missing includes may go unnoticed. Therefore, it makes sense to turn this feature off while doing GLib development, even if the compiler supports ELF - visibility attributes. The + visibility attributes. The option allows to do that. @@ -521,12 +521,12 @@ How to compile GLib itself By default the configure script will try - to auto-detect whether xsltproc + to auto-detect whether xsltproc and the necessary Docbook stylesheets are installed. If they are, then it will use them to rebuild the included - man pages from the XML sources. These options can be used + man pages from the XML sources. These options can be used to explicitly control whether man pages should be rebuilt - used or not. The distribution includes pre-generated man + used or not. The distribution includes pre-generated man pages. @@ -540,7 +540,7 @@ How to compile GLib itself to auto-detect whether the getxattr() family of functions is available. If it is, then extended attribute support will be included in GIO. These options can be used to - explicitly control whether extended attribute support + explicitly control whether extended attribute support should be included or not. getxattr() and friends can be provided by glibc or by the standalone libattr library. @@ -554,7 +554,7 @@ How to compile GLib itself By default the configure script will auto-detect if libselinux is available and include SELinux support in GIO if it is. These options can be - used to explicitly control whether SELinxu support should + used to explicitly control whether SELinux support should be included. -- 2.7.4