print errors on the osynctool's STDERR instead of only showing them in the traces

[chi70]

as seen in ticket #795 it is difficult for a user to understand whats going wrong as msynctool does not show any errors on the cli but only in the traces

Therefore I suggest to print these errors on the msynctool's STDERR instead of only showing them in the traces,

[dgollub]

Initial implemention with r3533.

Unfortunatley it's only enabled when also OSYNCTRACE is enabled.... We should make OSYNC_PRINTERROR independent of OSYNC_TRACE.

But OpenSync? build without tracing support should also keep OSYNC_PRINTERROR disabled. Purpose of OSYNC_PRINTERROR is to find "dirty" error handling which have to be fixed...

[chi70]

Replying to dgollub:

Initial implemention with r3533.

Unfortunatley it's only enabled when also OSYNCTRACE is enabled....

At least with OSYNC_TRACE set it looks really fine!

$msynctool --listplugins
ERROR: Unable to open module /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: undefined symbol: osync_objtype_sink_num_objformats
EXIT_ERROR: osync_module_load: Unable to open module /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: undefined symbol: osync_objtype_sink_num_objformats
Available plugins:
file-sync

$ unset OSYNC_TRACE
$ msynctool --listplugins
Available plugins:
file-sync

Thanks so far.

[tuju]

see ticket #630

[chi70]

Replying to tuju:

see ticket #630

#630 has a different target.

I verified with r3822, the behaviour is still the same. With OSYNC_TRACE set it works as expected.