Hi Norm,
you are probably using the subversion version of opensync. You then also
need multisync from subversion. I added new signals for batch committing
and the multisync 0.17 does not handle these so the compiler gives an error.
Armin
Norm Dressler wrote:
> Hi -- run into a problem compiling the multisync tool --
> make[2]: Entering directory
> `/home/norm/opensync/multisync-cli-0.90.17/tools'
> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/opensync-1.0 -Wall
> -Werror -I.. -g -O2 -MT msynctool.o -MD -MP -MF ".deps/msynctool.Tpo" -c
> -o msynctool.o msynctool.c; \
> then mv -f ".deps/msynctool.Tpo" ".deps/msynctool.Po"; else rm -f
> ".deps/msynctool.Tpo"; exit 1; fi
> msynctool.c: In function `member_status':
> msynctool.c:124: warning: enumeration value `MEMBER_COMMITTED_ALL' not
> handled in switch
> msynctool.c:124: warning: enumeration value `MEMBER_COMMITTED_ALL_ERROR'
> not handled in switch
> make[2]: *** [msynctool.o] Error 1
> make[2]: Leaving directory
> `/home/norm/opensync/multisync-cli-0.90.17/tools'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/norm/opensync/multisync-cli-0.90.17'
> make: *** [all] Error 2
>
> Is this the gcc version and the 'strict' issue or something else?
> Norm
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
|
