Testing a Windows build
Andreas Köhler
andi5.py at gmx.net
Thu Jan 15 17:26:00 EST 2009
Hi Stephen,
both, trunk and branches/2.2 should build libgsf 1.4.11 by default, but
the check in install.sh is rather limited. After all those changes, I
would recommend to run reset.sh.
Ciao,
-- andi5
Stephen Grant Brown schrieb:
> Hi All,
>
> I have just updated the Packaging dir on a Windows XP Machine vi svn
> update.
>
> I then run install.sh.
>
> It fixed a lot of conftest.c file not found erros which previously
> resulted in install.sh not running to completion.
>
> Now I get the following
>
> Extracting goffice-0.7.2.tar.bz2 ... done
> patching file `goffice/Makefile.am'
> patching file `goffice/utils/go-file.c'
> patching file `goffice/gtk/goffice-gtk.c'
> libtoolize: `/C/soft/autotools/share/aclocal/libtool.m4' is serial 48,
> less than 52 in `aclocal.m4'
> To remain compatible, you should update your `aclocal.m4' by running
> aclocal.
>
> --------------------------- snip
> -----------------------------------------------
> checking for GOFFICE... configure: error: Package requirements (
> glib-2.0 >= 2.8.0
> gobject-2.0 >= 2.16.0
> gmodule-2.0 >= 2.16.0
> gio-2.0 >= 2.16.0
> libgsf-1 >= 1.14.9
> libxml-2.0 >= 2.4.12
> pango >= 1.8.1
> pangocairo >= 1.8.1
> cairo >= 1.2.0
> cairo-svg >= 1.2.0
> cairo-pdf >= 1.2.0
> cairo-ps >= 1.2.0
>
> gtk+-2.0 >= 2.6.0
> libglade-2.0 >= 2.3.6
>
> gconf-2.0
> libgnomeui-2.0 >= 2.0.0
> ) were not met:
>
> Requested 'libgsf-1 >= 1.14.9' but version of libgsf-1 is 1.14.5
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables GOFFICE_CFLAGS
> and GOFFICE_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> What do I do to fix this?
>
> Yours sincerely Stephen Grant Brown
More information about the gnucash-devel
mailing list