Bug 586675 – Runtime library location

Introduce an option to specify the runtime location for libraries via
a relative path to libdir.

Signed-off-by: David Zeuthen <davidz@redhat.com>

docs/reference/glib/building.sgml

@@ -234,6 +234,9 @@ How to compile GLib itself
             <arg>--disable-selinux</arg>
             <arg>--enable-selinux</arg>
           </group>
+          <group>
+            <arg>--with-runtime-libdir=RELPATH</arg>
+          </group>
         </cmdsynopsis>
       </para>
 
@@ -555,6 +558,24 @@ How to compile GLib itself
 	  be included.
         </para>
      </formalpara>
+
+      <formalpara>
+        <title><systemitem>--with-runtime-libdir=RELPATH</systemitem></title>
+
+        <para>
+          Allows specifying a relative path to where to install the runtime
+          libraries (meaning library files used for running, not developing,
+          GLib applications). This can be used in operating system setups where
+          programs using GLib needs to run before e.g. <filename>/usr</filename>
+          is mounted.
+          For example, if LIBDIR is <filename>/usr/lib</filename> and
+          <filename>../../lib</filename> is passed to
+          <systemitem>--with-runtime-libdir</systemitem> then the
+          runtime libraries are installed into <filename>/lib</filename> rather
+          than <filename>/usr/lib</filename>.
+        </para>
+      </formalpara>
+
    </refsect1>
 
 </refentry>

docs/reference/glib/tmpl/fileutils.sgml

@@ -294,6 +294,23 @@ not be accessed directly.
 @Returns: 
 
 
+<!-- ##### FUNCTION g_mapped_file_ref ##### -->
+<para>
+
+</para>
+
+@file: 
+@Returns: 
+
+
+<!-- ##### FUNCTION g_mapped_file_unref ##### -->
+<para>
+
+</para>
+
+@file: 
+
+
 <!-- ##### FUNCTION g_mapped_file_free ##### -->
 <para>