xsltproc and Docbook packages do not enable this unexpectedly. Fixes
the build whenever manpages get enabled for some reason, as the PLIST
does not account for them.
- patch-ar and patch-as to avoid dependending on python are no longer
necessary since the introduction of --disable-modular-tests
- patch-co has been committed to glib in 2360d04e
- other patches cargo culted across
- statfs test was fixed in glib with commit afa82ae8
- no longer provide man pages as that requires docbook & xsltproc
Many changes in glib since 2.32.4, especially GDBus improvements.
See NEWS file http://git.gnome.org/browse/glib/plain/NEWS?id=2.34.0 for details.
On a 32-bit OpenIndiana 151a machine, glib2 failed with the error:
"large files are not supported by libelf".
The glib2 makefile doesn't include libelf from pkgsrc, it uses the version
with the header at /usr/include/libelf.h. Libelf will only support large
files (64 bits) with 64-bit versions of SunOS.
This change adds additional checks. When the Makefile determines that the
package is building on a 32-bit SunOS, it will force the configure script
to define _FILE_OFFSET_BITS as 32 which allows glib2 to build completely.
No need to bump revision; it wouldn't have built on 32-bit SunOS before.
This is a poor fix for an apparently not well understood problem, so
we should consider it a stopgap fix and find a sustainable solution
after the freeze.
* Bug fixes:
Correct a typo in the ELF configure check
Reset LIBS after the ELF configure check
Fix GIO/GObject Visual C++ projects
gio: fix error handling in async case of GProxy...
GConverterInputStream: fix an infinite loop...
* Translation updates:
Bulgarian
Catalan
Czech
German
Japanese
Slovenian
Telugu
* Restore pthread flag settings in configure script.
It still in the last hunk of patch-ak (for configure.ac),
but lost at updated to 2.32.1.
* Fixes missing pthread linkage of libglib-2.0 on OpenBSD.
Bump PKGREVISION.
* GApplication: can now have a NULL application ID
* g_clear_object: fix warnings when using it on C++ (due to lack of
ability to implicitly cast void*)
* GDBus:
- add our own implementation of the message bus for use on Windows only
- fix up a few bugs that use of this bus uncovered in GDBus
- escape nonce files in dbus addressess (think 'c:\')
- support initial underscores in dbus codegen namespace (for private)
* Fix misdetection of GNUstep as Cocoa (for the MacOS GSettings backend)
* make sure configure fails if AC_CHECK_ALIGNOF cannot detect the alignment
* GAppInfo: overwrite the DISPLAY only if it is set in the launch context
* glib/tests/date: force US locale running the GDateTime tests
* GSocketControlMessage: Don't warn about unknown messages
* Resources:
- fix broken use of GVDB on big endian machines
- set a 'display name' so that pretty file names appear in Gtk CSS
warning messages
* GMainContext:
- block child sources when blocking the parent
- introduce more testcases for child sources
* Translations updates:
Brazilian Portuguese
French
Galician
Italian
Lithuanian
Polish
Polish
Serbian
Simplified Chinese
Spanish
* Bug fixed:
619026 avoid warning in gutils.h when using gcc with -Wconversion
669260 Open/Save dialog hangs waiting for data with libsoup
671249 GApplication: Allow a null application_id?
672786 goa-daemon: action in notification doesn't work
673409 g_resource_lookup_data may return stale data pointer
674172 glib-2.32.1 misdetects GNUstep as Cocoa
674345 cssprovider: Make sure to print out file name in css warnings
674483 broken configure results when cross-compiling with gcc >= 4.5
and... well, the kqueue support is built but not used!
Now, running a test program provided by Dmitry DTRT (with the exception
of two tests, which seem to be not working in macppc). Ride the previous
revision bump.
the Google Summer of Code 2011 program. Congratulations, Dmitry! :-)
This comes in the form of a new 'kqueue' build-time option. This should NOT
be an option, but it is for two reasons:
- I consider this still experimental for it to be enabled on everyone's
machines, and the code is not "official".
- The patch requires us to run automake/autoconf during the pre-configure
stage, and I don't want to add these dependencies on the default package
build.
When these patches get integrated upstream, we can get rid of the option
altogether.
Also note that I had to backport some of our custom changes to Makefile.in
files and some to configure to the original Makefile.am files and
configure.ac. This is to prevent our custom patches from being lost during
the automake/autoconf invocations we now do when 'kqueue' is enabled.
Bump PKGREVISION to 1.
