Just use a config.h geneated for Mac OS X for now, tweak later if
necesssary.

I don't know if this is the right thing to do. The --disable-python
switch is documented to "Disable build of Python 2.x UNO API". Does
that mean that it should disable use of Python at run-time completely?
What about use of Python tools at build-time, do we have such? Will
--disable-python then disable their use, too?

Don't use the same name for the GLib DLLs that we build with MSVS9 as
in the "official" MinGW-built packages (either the ones from
www.gtk.org, or the ones from OBS). The "official" GLib DLLs use
msvcrt.dll, while the ones we build use msvcr90.dll. We want to avoid
potential confusion. Call the DLLs we build glib-2.0.dll etc, not
libglib-2.0-0.dll etc.

Conflicts:
	berkeleydb/makefile.mk

Conflicts:
	python/makefile.mk
	zlib/makefile.mk

Based on the old novell-win32-agfa-monotype-fonts.diff patch.

Conflicts:
	dictionaries/de_AT/README_extension_owner.txt
	dictionaries/de_AT/makefile.mk
	dictionaries/de_CH/makefile.mk
	dictionaries/de_DE/makefile.mk
	dictionaries/prj/build.lst

Signed-off-by: Petr Mladek <pmladek@suse.cz>
Signed-off-by: Michael Meeks <michael.meeks@novell.com>
Signed-off-by: Fridrich Strba <fridrich.strba@graduateinstitute.ch>

no doubt not the right fix but gets the build over the hump

Branch "libreoffice-3-4" has been created. Further changes in master
will be used for LibreOffice-3.5 release.