Planner-list PostgreSQL & Planner

[John Spikowski <support scriptbasic org>]

Hi List,

I manage the ScriptBasic open source project and I was looking at was to
externally script or embed ScriptBasic in Planner.

I have been trying to get database support going with planner on Ubuntu
10.10 (32 bit) and I run into this make error. If I don't use the
--with-database option, Planner compiles fine.

./configure --with-database

Planner prefix               : /usr/local
Build API docs               : no
Python bindings              : yes
Python plugin                : no
Simple priority scheduling   : no
Database/GDA support         : yes, 30
Evolution Data Server import : no
Evolution Data Server backend: no

So fare so good. 

# make
make  all-recursive
make[1]: Entering directory `/home/jrs/planner'
Making all in po
make[2]: Entering directory `/home/jrs/planner/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/jrs/planner/po'
Making all in libplanner
make[2]: Entering directory `/home/jrs/planner/libplanner'
  CC     libstorage_sql_la-mrp-sql.lo
cc1: warnings being treated as errors
mrp-sql.c: In function ‘sql_write_project’:
mrp-sql.c:2417: error: format not a string literal and no format
arguments
mrp-sql.c:2424: error: format not a string literal and no format
arguments
mrp-sql.c:2447: error: format not a string literal and no format
arguments
mrp-sql.c:2514: error: format not a string literal and no format
arguments
mrp-sql.c: In function ‘mrp_sql_save_project’:
mrp-sql.c:3729: error: format not a string literal and no format
arguments
make[2]: *** [libstorage_sql_la-mrp-sql.lo] Error 1
make[2]: Leaving directory `/home/jrs/planner/libplanner'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jrs/planner'
make: *** [all] Error 2

This makes fine if I don't include PostgreSQL database support via
libgda-3.0

There looks to be a 'hack' for 

WRITE_ERROR (error, data->con);

#define WRITE_ERROR(e,c) \
G_STMT_START \
{ g_set_error(e,MRP_ERROR,MRP_ERROR_SAVE_WRITE_FAILED,
sql_get_last_error (c)); } \
G_STMT_END

I'm wondering if G_STMT stuff is being ignored. The other thought is
that if I could turn off warning that turn into errors, maybe this would
make for me. 

Any nudge in the right direction would be appreciated.

John