[csw-maintainers] Issues with openjade when compiling glib 1.3.15

Dagobert Michelsen dam at opencsw.org
Wed May 13 12:10:25 CEST 2009


Hi,

I am currently updating glib (version 1.x) to 1.3.15 and
get the attached errors on compilation. I don't really
understand how this SGML/XML stuff works, so maybe someone
who as more expertise may have a look?

The package has been committed to mGAR as pkg/glib.


Best regards

   -- Dago



...
/opt/csw/bin/openjade:I: maximum number of errors (200) reached;  
change with -E option
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:1:73:W:  
cannot generate system identifier for public text "-//James Clark//DTD  
DSSSL Style Sheet//EN"
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:2:91:W:  
cannot generate system identifier for public text "-//Norman Walsh// 
DOCUMENT DocBook HTML Stylesheet//EN"
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:3:0:E:  
reference to entity "STYLE-SHEET" for which no system identifier could  
be generated
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:1:0:  
entity was defined here
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:3:0:E:  
DTD did not contain element declaration for document type name
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:2:0:E:  
notation "DSSSL" for entity "dbstyle" undefined
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:5:12:E:  
element "STYLE-SHEET" undefined
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:6:25:E:  
there is no attribute "USE"
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:6:34:E:  
element "STYLE-SPECIFICATION" undefined
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl:7:25:E:  
element "STYLE-SPECIFICATION-BODY" undefined
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl: 
463:27:E: there is no attribute "ID"
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl: 
463:46:E: there is no attribute "DOCUMENT"
/opt/csw/bin/openjade:/opt/csw/share/gtk-doc/data/gtk-doc.dsl: 
463:55:E: element "EXTERNAL-SPECIFICATION" undefined
/opt/csw/bin/openjade:I: (invalid message)
       GLib Reference Manual


       GLib Overview
     GLib is a general-purpose utility library, which provides many  
useful data
types, macros, type conversions, string utilities, file utilities, a  
main
loop abstraction, and so on. It works on many UNIX-like platforms,  
Windows,
OS/2 and BeOS. GLib is released under the GNU Library General Public  
License
(GNU LGPL).

     GLib depends on the following:

iconv()
In order to implement conversions between character sets,
GLib requires an implementation of the standard iconv()
routine. Most modern systems will have a suitable implementation,  
however
many older systems lack an iconv() implementation. On
such systems, you must install the
libiconv library.

a thread implementation
The thread support in GLib can be based upon several native thread
implementations, e.g. POSIX threads, DCE threads or Solaris threads.



     Compiling the GLib package
3
GLib Library

Compiling the GLib Package
How to compile GLib itself

           Building the Library on UNIX
               On UNIX, GLib uses the standard GNU build system,
         using autoconf for package
         configuration and resolving portability issues,
         automake for building makefiles
         that comply with the GNU Coding Standards, and
         libtool for building shared
         libraries on multiple platforms.  The normal sequence for
         compiling and installing the GLib library is thus:

                   ./configure
           make
           make install



               The standard options provided by GNU
         autoconf may be passed to the
         configure script.  Please see the
         autoconf documentation or run
         ./configure --help for information about
         the standard options.



           Extra Configuration Options

               In addition to the normal options, the
         configure script in the GTK+
         library supports these additional arguments:

                   configure
                       --enable-debug=[no|minimum|yes]

                       --disable-gc-friendly
             --enable-gc-friendly

                       --disable-mem-pools
             --enable-mem-pools

                       --disable-threads
             --enable-threads

                       --with-threads=[none|posix|dce|solaris|win32]

                       --disable-gtk-doc
             --enable-gtk-doc




               --enable-debug

                  Turns on various amounts of debugging support.  
Setting this to 'no'
          disables g_assert(), g_return_if_fail(),  
g_return_val_if_fail() and
          all cast checks between different object types. Setting it  
to 'minimum'         disables only cast checks. Setting it to 'yes'  
enables
          runtime debugging.
          The default is 'minimum'.
          Note that 'no' is fast, but dangerous as it tends to  
destabilize
          even mostly bug-free software by changing the effect of many  
bugs
          from simple warnings into fatal crashes. Thus
          --enable-debug=no should not
          be used for stable releases of gtk+.



               --disable-gc-friendly and
           --enable-gc-friendly

                   When enabled all memory freed by the application,
           but retained by GLib for performance reasons
           is set to zero, thus making deployed garbage
           collection or memory profiling tools detect
           unlinked memory correctly. This will make GLib
           slightly slower and is thus disabled by default.



               --disable-mem-pools and
           --enable-mem-pools

               Many small chunks of memory are often allocated via  
collective pools
         in GLib and are cached after release to speed up reallocations.
         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
         this:
                                  GList, GSList,
          GNode allocations


                         GMemChunks become basically non-effective


                          GSignal disables all caching (potentially
          very slow)


                          GType doesn't honour the
          GTypeInfo
          n_preallocs field anymore


                          the GBSearchArray flag
          G_BSEARCH_ALIGN_POWER2 becomes non-functional






               --disable-threads and
           --enable-threads

                    Do not compile GLib to be multi thread safe. GLib
            will be slightly faster then. This is however not
            recommended, as many programs rely on GLib being
            multi thread safe.



               --with-threads

                   Specify a thread implementation to use.
                                         'posix' and 'dce' can be used  
interchangeable
                 to mean the different versions of posix
                 threads. configure tries to find out, which
                 one is installed.


                               'solaris' uses the native Solaris  
thread implementation.


                               'none' means that GLib will be thread  
safe,
                 but does not have a default thread
                 implementation. This has to be supplied to
                 g_thread_init() by the programmer.






               --disable-gtk-doc and
           --enable-gtk-doc

                   By default the configure script will try
           to auto-detect whether the
           gtk-doc package is installed.  If
           it is, then it will use it to extract and build the
           documentation for the GLib library.  These options
           can be used to explicitly control whether
           gtk-doc should be
           used or not.  If it is not used, the distributed,
           pre-generated HTML files will be installed instead of
           building them on your machine.






     Compiling GLib Applications
3
GLib Library

Compiling GLib Applications
How to compile your GLib application

Compiling GLib Applications on UNIX

To compile a GLib application, you need to tell the compiler where to
find the GLib header files and libraries. This is done with the
pkg-config utility.
The following interactive shell session demonstrates how
pkg-config is used:
$ pkg-config --cflags glib-2.0
  -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
$ pkg-config --libs glib-2.0
  -L/usr/lib -lm -lglib-1.3
If your application uses modules, threads or GObject
features, it must be compiled and linked with the options returned by  
the
following pkg-config invokations:
$ pkg-config --cflags --libs gmodule-2.0
$ pkg-config --cflags --libs gthread-2.0
$ pkg-config --cflags --libs gobject-2.0
The simplest way to compile a program is to use the "backticks"
feature of the shell. If you enclose a command in backticks
(not single quotes), then its output will be
substituted into the command line before execution. So to compile
a GLib Hello, World, you would type the following:
$ cc `pkg-config --cflags --libs glib-2.0` hello.c -o hello



     Running GLib Applications
3
GLib Library

Running GLib Applications
How to run and debug your GLib application

Running and debugging GLib Applications

Environment variables


GLib inspects a few of environment variables in addition to standard
variables like LANG, PATH or HOME.

   G_BROKEN_FILENAMES

       If this environment variable is set, GLib assumes that  
filenames are in
     the locale encoding rather than in UTF-8.


   G_MESSAGES_PREFIXED

       A list of log levels for which messages should be prefixed by the
     program name and PID of the application. The default is to prefix
     everything except G_LOG_LEVEL_MESSAGE and G_LOG_LEVEL_INFO.


   G_DEBUG

       If GLib has been configured with --enable-debug=yes,
     this variable can be set to a list of debug options, which cause  
GLib
     to print out different types of debugging information.
                   fatal_warnings
         Causes GLib to abort the program at the first call
            to g_warning(). This option is
            special in that it doesn't require GLib to be configured  
with
            debugging support.






Traps and traces
gmake[6]: *** [html-build.stamp] Error 1
gmake[6]: Leaving directory `/home/dam/mgar/pkg/glib/trunk/work/build- 
isa-sparcv8/glib-1.3.15/docs/reference/glib'
gmake[5]: *** [all-recursive] Error 1




More information about the maintainers mailing list