opensync-users

[Opensync-users] OpenSync 0.15 released

[Armin B. <arm...@de...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I just released OpenSync 0.15. This is the first release that has all
plugins split out completely from the framework.

The new features are:

- - The plugins now have 2 possibilites to do batch commits if they like.
The first option is that they receive the changes just normal and get a
committed_all signal as soon as opensync is done sending the changes.
The second option is that they implement a batch commit function that is
called by opensync with an array of all changes to commit.

- - All public functions are now documented via doxygen

- - Improved comparison of vevent and vtodo objects

- - New "most recent" conflict resultion policy: The user can now solve a
conflict by choosing the newest object.

- - Renamed opensync to libopensync to make clear that it is just a libary.

- - the unit tests are now utilizing a special mock-plugin that lives in
the tests/ directoy. This makes it far easier to run and extend the tests.

- - the sources are now compatible with rpm building

Armin




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCS+btq9z7v9k9UakRAhtzAJ9eCWmGfYswrmQ45NGaf9vcxz/jAgCfYNfy
d2ZwprnUAn+bmevWlYNaIvE=
=2Wu0
-----END PGP SIGNATURE-----

Re: [Opensync-users] OpenSync 0.15 released

[Dave H. <sk...@ph...>]

Hi all,

Just thought I would throw a question out here primarily for Armin, but
I am happy to hear what others thing.

Have you looked at GroupDAV (http://www.groupdav.org/)?  If so do you
have any plans to use it?

I am still sitting on the fence on GroupDAV, so I am curious to see what
others are thing about it.  For openSync I think it could help broaden
the appeal of the project and also for groupware projects which
implement the protocol.  I can also see the case for everyone just using
syncML ;)

Cheers

Dave

On Thu, 2005-03-31 at 14:02 +0200, Armin Bauer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> I just released OpenSync 0.15. This is the first release that has all
> plugins split out completely from the framework.
> 
> The new features are:
> 
> - - The plugins now have 2 possibilites to do batch commits if they like.
> The first option is that they receive the changes just normal and get a
> committed_all signal as soon as opensync is done sending the changes.
> The second option is that they implement a batch commit function that is
> called by opensync with an array of all changes to commit.
> 
> - - All public functions are now documented via doxygen
> 
> - - Improved comparison of vevent and vtodo objects
> 
> - - New "most recent" conflict resultion policy: The user can now solve a
> conflict by choosing the newest object.
> 
> - - Renamed opensync to libopensync to make clear that it is just a libary.
> 
> - - the unit tests are now utilizing a special mock-plugin that lives in
> the tests/ directoy. This makes it far easier to run and extend the tests.
> 
> - - the sources are now compatible with rpm building
> 
> Armin
> 
> 
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFCS+btq9z7v9k9UakRAhtzAJ9eCWmGfYswrmQ45NGaf9vcxz/jAgCfYNfy
> d2ZwprnUAn+bmevWlYNaIvE=
> =2Wu0
> -----END PGP SIGNATURE-----
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/Info/Sentarus/hamr30
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare
-------------------------------------------------------------------------
Do you think if Bill Gates got laid in high school, do you think there'd 
be a Microsoft?  Of course not.
Underwear Goes Inside The Pants by Lazy Boy

Re: [Opensync-users] OpenSync 0.15 released

[Armin B. <arm...@de...>]

Dave Hall wrote:

>Hi all,
>
>Just thought I would throw a question out here primarily for Armin, but
>I am happy to hear what others thing.
>
>Have you looked at GroupDAV (http://www.groupdav.org/)? If so do you
>have any plans to use it?
>

Yes, support for the *DAV protocols is definetly a target.

>I am still sitting on the fence on GroupDAV, so I am curious to see what
>others are thing about it. For openSync I think it could help broaden
>the appeal of the project and also for groupware projects which
>implement the protocol. I can also see the case for everyone just using
>syncML ;)

How is groupdav related to caldav and webdav?
There already is a plugin in the old multisync that can pull icalendar 
files from webdav, sync it and put it back (thats whats called caldev 
afaik).

>
>Cheers
>
>Dave
>
>On Thu, 2005-03-31 at 14:02 +0200, Armin Bauer wrote:
>

> Hi,
>
> I just released OpenSync 0.15. This is the first release that has all
> plugins split out completely from the framework.
>
> The new features are:
>
> - The plugins now have 2 possibilites to do batch commits if they like.
> The first option is that they receive the changes just normal and get a
> committed_all signal as soon as opensync is done sending the changes.
> The second option is that they implement a batch commit function that is
> called by opensync with an array of all changes to commit.
>
> - All public functions are now documented via doxygen
>
> - Improved comparison of vevent and vtodo objects
>
> - New "most recent" conflict resultion policy: The user can now solve a
> conflict by choosing the newest object.
>
> - Renamed opensync to libopensync to make clear that it is just a libary.
>
> - the unit tests are now utilizing a special mock-plugin that lives in
> the tests/ directoy. This makes it far easier to run and extend the tests.
>
> - the sources are now compatible with rpm building
>
> Armin
>
>
>
>

-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
_______________________________________________
Opensync-users mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] OpenSync 0.15 released

[Helge H. <hel...@op...>]

On Mar 31, 2005, at 15:11, Armin Bauer wrote:
>> I am still sitting on the fence on GroupDAV, so I am curious to see 
>> what
>> others are thing about it. For openSync I think it could help broaden
>> the appeal of the project and also for groupware projects which
>> implement the protocol. I can also see the case for everyone just 
>> using
>> syncML ;)
> How is groupdav related to caldav and webdav?

GroupDAV is mostly a subset of CalDAV for vevent/vtodo related 
operations. It also works with vcards in addition, something which 
isn't in the scope of CalDAV.

The focus of GroupDAV is to be really, really simple to implement in 
web based groupware servers. It doesn't even require a full WebDAV 
implementation, just two predefined PROPFIND queries.

An idea is to have something usable very quickly (GroupDAV) but to have 
a reasonable base to build full CalDAV support upon.

> There already is a plugin in the old multisync that can pull icalendar 
> files from webdav, sync it and put it back (thats whats called caldev 
> afaik).

I guess this plugin is doing iCal-over-HTTP. The difference to CalDAV 
and GroupDAV is that those are using URLs to address individual 
vevent/vtodo entries with all the attached advantages.

Greets,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org

Re: [Opensync-users] OpenSync 0.15 released

[Armin B. <arm...@de...>]

Helge Hess wrote:

> On Mar 31, 2005, at 15:11, Armin Bauer wrote:
>
>>> I am still sitting on the fence on GroupDAV, so I am curious to see 
>>> what
>>> others are thing about it. For openSync I think it could help broaden
>>> the appeal of the project and also for groupware projects which
>>> implement the protocol. I can also see the case for everyone just using
>>> syncML ;)
>>
>> How is groupdav related to caldav and webdav?
>
>
> GroupDAV is mostly a subset of CalDAV for vevent/vtodo related 
> operations. It also works with vcards in addition, something which 
> isn't in the scope of CalDAV.
>
> The focus of GroupDAV is to be really, really simple to implement in 
> web based groupware servers. It doesn't even require a full WebDAV 
> implementation, just two predefined PROPFIND queries.
>
> An idea is to have something usable very quickly (GroupDAV) but to 
> have a reasonable base to build full CalDAV support upon.

What advantages does caldav have over groupdav?

Are there any special libraries necessary or can groupdav / caldav be 
used with the normal webdav libraries (like libneon)?

>
>> There already is a plugin in the old multisync that can pull 
>> icalendar files from webdav, sync it and put it back (thats whats 
>> called caldev afaik).
>
>
> I guess this plugin is doing iCal-over-HTTP. The difference to CalDAV 
> and GroupDAV is that those are using URLs to address individual 
> vevent/vtodo entries with all the attached advantages.

right. the plugins just pulls the complete file but not indiviual entries.

>
> Greets,
>   Helge

Re: [Opensync-users] OpenSync 0.15 released

[Helge H. <hel...@op...>]

On Mar 31, 2005, at 16:52, Armin Bauer wrote:
> What advantages does caldav have over groupdav?

CalDAV specifies several queries on calendaring data, for example "give 
me all events from 2004-03-12 to 2004-03-18". Such a query will even 
expand recurrences etc if requested to do so.
This is irrelevant for GroupDAV where such functionality is performed 
by the local client on its local cache of the calendaring/contact data.

GroupDAV is just a synchronisation protocol based on HTTP etags with 
tiny bits of WebDAV to discover the resources of a collection.

> Are there any special libraries necessary or can groupdav / caldav be 
> used with the normal webdav libraries (like libneon)?

You can use the normal WebDAV libraries. Kontact GroupDAV support uses 
the regular KDE WebDAV resource and AFAIK the Noodle plugin for 
Evolution uses libsoup.

Using a complete WebDAV library might be unnecessary. A client only 
needs to be able to parse two very specific PROPFIND result. A simple 
SAX handler and a generic HTTP client lib would probably do for that.

Greets,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org

Re: [Opensync-users] OpenSync 0.15 released

[Armin B. <arm...@de...>]

Helge Hess wrote:

> On Mar 31, 2005, at 16:52, Armin Bauer wrote:
>
>> What advantages does caldav have over groupdav?
>
>
> CalDAV specifies several queries on calendaring data, for example 
> "give me all events from 2004-03-12 to 2004-03-18". Such a query will 
> even expand recurrences etc if requested to do so.
> This is irrelevant for GroupDAV where such functionality is performed 
> by the local client on its local cache of the calendaring/contact data.
>
> GroupDAV is just a synchronisation protocol based on HTTP etags with 
> tiny bits of WebDAV to discover the resources of a collection.

ah i see. would it be possible to issue a query like "give me all events 
that have been changes since the last sync" or will this information 
have to be maintained locally (which would be bad since we would need to 
transfer all items to calculate the hash)?

>
>> Are there any special libraries necessary or can groupdav / caldav be 
>> used with the normal webdav libraries (like libneon)?
>
>
> You can use the normal WebDAV libraries. Kontact GroupDAV support uses 
> the regular KDE WebDAV resource and AFAIK the Noodle plugin for 
> Evolution uses libsoup.
>
> Using a complete WebDAV library might be unnecessary. A client only 
> needs to be able to parse two very specific PROPFIND result. A simple 
> SAX handler and a generic HTTP client lib would probably do for that.
>
> Greets,
>   Helge

Re: [Opensync-users] OpenSync 0.15 released

[Helge H. <hel...@op...>]

On Mar 31, 2005, at 17:17, Armin Bauer wrote:
> ah i see. would it be possible to issue a query like "give me all 
> events that have been changes since the last sync"

No, this is SyncML ;-)

> or will this information have to be maintained locally (which would be 
> bad since we would need to transfer all items to calculate the hash)?

The synchronisation is based on HTTP etags. To calculate the set 
difference (added/delete/changed URLs) you need to retrieve the etag, 
not the actual content.
This is one of the PROPFIND queries you need to implement, its in 
section 5.1 of the draft-01:
   http://www.groupdav.org/draft-hess-groupdav-01.html

Yes, this only works well up to a certain size of a folder (depending 
on the speed of the connection). Fortunately WebDAV results compress 
very well (deflate content-transfer-encoding), so the response size is 
reasonable and the operation itself is fast on most/all servers.
It will work well for some 10.000 objects per collection, but certainly 
breaks if it contains 100.000. So its fine for about 28 years of 
calendaring data, which is OK for us ;-)

Another disadvantage is that the first sync between client and server 
will be rather slow (will issue a separate HTTP GET request per 
object). But since this is a once-per-client operation, we considered 
this reasonable too.

Greets,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org

[Opensync-users] Debian repository

[Matthew K. <m_...@fa...>]

I see that there are packages for Debian available on the homepage - any
chance of someone setting up a repository so we can apt-get these
packages? The instructions can be found here:

http://www.debian.org/doc/manuals/repository-howto/repository-howto.html

Many thanks,
Matt
--
M.Sc. Computer Science student       
Imperial College, London          

256a Archway Road,
London,
N6 5AX

tel       07717 204242

Re: [Opensync-users] OpenSync 0.15 released

[Esteban M. <zo...@fo...>]

On Thu, Mar 31, 2005 at 02:02:53PM +0200, Armin Bauer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hi,
>=20
> I just released OpenSync 0.15. This is the first release that has all
> plugins split out completely from the framework.
> [...]

   I can't compile it :-?

-------------------------------- 8< --------------------------------
zoso@velutha:~/src/opensync/libopensync-0.15$ make
cd . && /bin/bash ./config.status config.h
config.status: creating config.h
make  all-recursive
make[1]: Entering directory `/home/zoso/src/opensync/libopensync-0.15'
Making all in opensync
make[2]: Entering directory `/home/zoso/src/opensync/libopensync-0.15/ope=
nsync'
Makefile:340: .deps/opensync_anchor.Plo: No existe el fichero o el direct=
orio
Makefile:341: .deps/opensync_change.Plo: No existe el fichero o el direct=
orio
Makefile:342: .deps/opensync_changecmds.Plo: No existe el fichero o el di=
rectorio
Makefile:343: .deps/opensync_context.Plo: No existe el fichero o el direc=
torio
Makefile:344: .deps/opensync_convert.Plo: No existe el fichero o el direc=
torio
Makefile:345: .deps/opensync_convreg.Plo: No existe el fichero o el direc=
torio
Makefile:346: .deps/opensync_db.Plo: No existe el fichero o el directorio
Makefile:347: .deps/opensync_debug.Plo: No existe el fichero o el directo=
rio
Makefile:348: .deps/opensync_env.Plo: No existe el fichero o el directori=
o
Makefile:349: .deps/opensync_error.Plo: No existe el fichero o el directo=
rio
Makefile:350: .deps/opensync_filter.Plo: No existe el fichero o el direct=
orio
Makefile:351: .deps/opensync_group.Plo: No existe el fichero o el directo=
rio
Makefile:352: .deps/opensync_hashtable.Plo: No existe el fichero o el dir=
ectorio
Makefile:353: .deps/opensync_member.Plo: No existe el fichero o el direct=
orio
Makefile:354: .deps/opensync_plugin.Plo: No existe el fichero o el direct=
orio
Makefile:355: .deps/opensync_user.Plo: No existe el fichero o el director=
io
make[2]: *** No hay ninguna regla para construir el objetivo `.deps/opens=
ync_user.Plo'.  Alto.
make[2]: Leaving directory `/home/zoso/src/opensync/libopensync-0.15/open=
sync'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/zoso/src/opensync/libopensync-0.15'
make: *** [all] Error 2
-------------------------------- >8 --------------------------------

And, just in case it matters:

-------------------------------- 8< --------------------------------
zoso@velutha:~/src/opensync/libopensync-0.15$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
[...]
checking for glib-2.0 gmodule-2.0 gobject-2.0 gthread-2.0 sqlite3... yes
checking PACKAGE_CFLAGS... -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include =20
checking PACKAGE_LIBS... -Wl,--export-dynamic -pthread -lgmodule-2.0 -ldl
-lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lsqlite3 =20
configure: creating ./config.status
config.status: creating Makefile
config.status: creating opensync/Makefile
config.status: creating tools/Makefile
config.status: creating tests/Makefile
config.status: error: cannot find input file: tests/mock-plugin/Makefile.=
in
-------------------------------- >8 --------------------------------

There is only a Makefile.am and some mock_*.{c,h} in tests/mock-plugin/.

--=20
Esteban Manchado Vel=E1zquez <zo...@fo...> - http://www.foton.es
EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es

Re: [Opensync-users] OpenSync 0.15 released

[Armin B. <arm...@de...>]

you have to run ./autogen.sh before compiling. this bug (the missing
Makefile.in in the mock-plugin directory) will be fixed in the next release.

Esteban Manchado Velázquez wrote:
> On Thu, Mar 31, 2005 at 02:02:53PM +0200, Armin Bauer wrote:
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Hi,
>>
>>I just released OpenSync 0.15. This is the first release that has all
>>plugins split out completely from the framework.
>>[...]
>
>
>    I can't compile it :-?
>
> -------------------------------- 8< --------------------------------
> zoso@velutha:~/src/opensync/libopensync-0.15$ make
> cd . && /bin/bash ./config.status config.h
> config.status: creating config.h
> make  all-recursive
> make[1]: Entering directory `/home/zoso/src/opensync/libopensync-0.15'
> Making all in opensync
> make[2]: Entering directory `/home/zoso/src/opensync/libopensync-0.15/opensync'
> Makefile:340: .deps/opensync_anchor.Plo: No existe el fichero o el directorio
> Makefile:341: .deps/opensync_change.Plo: No existe el fichero o el directorio
> Makefile:342: .deps/opensync_changecmds.Plo: No existe el fichero o el directorio
> Makefile:343: .deps/opensync_context.Plo: No existe el fichero o el directorio
> Makefile:344: .deps/opensync_convert.Plo: No existe el fichero o el directorio
> Makefile:345: .deps/opensync_convreg.Plo: No existe el fichero o el directorio
> Makefile:346: .deps/opensync_db.Plo: No existe el fichero o el directorio
> Makefile:347: .deps/opensync_debug.Plo: No existe el fichero o el directorio
> Makefile:348: .deps/opensync_env.Plo: No existe el fichero o el directorio
> Makefile:349: .deps/opensync_error.Plo: No existe el fichero o el directorio
> Makefile:350: .deps/opensync_filter.Plo: No existe el fichero o el directorio
> Makefile:351: .deps/opensync_group.Plo: No existe el fichero o el directorio
> Makefile:352: .deps/opensync_hashtable.Plo: No existe el fichero o el directorio
> Makefile:353: .deps/opensync_member.Plo: No existe el fichero o el directorio
> Makefile:354: .deps/opensync_plugin.Plo: No existe el fichero o el directorio
> Makefile:355: .deps/opensync_user.Plo: No existe el fichero o el directorio
> make[2]: *** No hay ninguna regla para construir el objetivo `.deps/opensync_user.Plo'.  Alto.
> make[2]: Leaving directory `/home/zoso/src/opensync/libopensync-0.15/opensync'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/zoso/src/opensync/libopensync-0.15'
> make: *** [all] Error 2
> -------------------------------- >8 --------------------------------
>
> And, just in case it matters:
>
> -------------------------------- 8< --------------------------------
> zoso@velutha:~/src/opensync/libopensync-0.15$ ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> [...]
> checking for glib-2.0 gmodule-2.0 gobject-2.0 gthread-2.0 sqlite3... yes
> checking PACKAGE_CFLAGS... -pthread -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include
> checking PACKAGE_LIBS... -Wl,--export-dynamic -pthread -lgmodule-2.0 -ldl
> -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lsqlite3
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating opensync/Makefile
> config.status: creating tools/Makefile
> config.status: creating tests/Makefile
> config.status: error: cannot find input file: tests/mock-plugin/Makefile.in
> -------------------------------- >8 --------------------------------
>
> There is only a Makefile.am and some mock_*.{c,h} in tests/mock-plugin/.
>

Re: [Opensync-users] OpenSync 0.15 released

[Matthew K. <m_...@fa...>]

>    I can't compile it :-?

I get exactly the same output as Esteban - I definitely have dbus-dev
installed, so I'm not sure what I'm doing wrong. Sorry, I'm not much
good with makefiles...:-(

matt@mkay-t42:~/dev/osync/libopensync-0.15$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for strerror in -lcposix... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag  works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for bison... no
checking for byacc... no
checking for pkg-config... /usr/bin/pkg-config
checking for libxml-2.0... yes
checking XML_CFLAGS... -I/usr/include/libxml2
checking XML_LIBS... -lxml2 -lpthread -lz -lm
checking check.h usability... no
checking check.h presence... no
checking for check.h... no
configure: Checking to see if we can build Python bindings
checking for a Python interpreter with version >= 2.2... python
checking for python... /usr/bin/python
checking for python version... 2.3
checking for python platform... linux2
checking for python script directory...
${prefix}/lib/python2.3/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.3/site-packages
checking for pyrexc... no
checking for headers required to compile python extensions... found
checking for glib-2.0 gmodule-2.0 gobject-2.0 gthread-2.0 sqlite3... yes
checking PACKAGE_CFLAGS... -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include
checking PACKAGE_LIBS... -Wl,--export-dynamic -pthread -lgmodule-2.0
-ldl -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lsqlite3
configure: creating ./config.status
config.status: creating Makefile
config.status: creating opensync/Makefile
config.status: creating tools/Makefile
config.status: creating tests/Makefile
config.status: error: cannot find input file:
tests/mock-plugin/Makefile.in



matt@mkay-t42:~/dev/osync/libopensync-0.15$ make
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make  all-recursive
make[1]: Entering directory `/home/matt/dev/osync/libopensync-0.15'
Making all in opensync
make[2]: Entering directory
`/home/matt/dev/osync/libopensync-0.15/opensync'
Makefile:340: .deps/opensync_anchor.Plo: No such file or directory
Makefile:341: .deps/opensync_change.Plo: No such file or directory
Makefile:342: .deps/opensync_changecmds.Plo: No such file or directory
Makefile:343: .deps/opensync_context.Plo: No such file or directory
Makefile:344: .deps/opensync_convert.Plo: No such file or directory
Makefile:345: .deps/opensync_convreg.Plo: No such file or directory
Makefile:346: .deps/opensync_db.Plo: No such file or directory
Makefile:347: .deps/opensync_debug.Plo: No such file or directory
Makefile:348: .deps/opensync_env.Plo: No such file or directory
Makefile:349: .deps/opensync_error.Plo: No such file or directory
Makefile:350: .deps/opensync_filter.Plo: No such file or directory
Makefile:351: .deps/opensync_group.Plo: No such file or directory
Makefile:352: .deps/opensync_hashtable.Plo: No such file or directory
Makefile:353: .deps/opensync_member.Plo: No such file or directory
Makefile:354: .deps/opensync_plugin.Plo: No such file or directory
Makefile:355: .deps/opensync_user.Plo: No such file or directory
make[2]: *** No rule to make target `.deps/opensync_user.Plo'.  Stop.
make[2]: Leaving directory
`/home/matt/dev/osync/libopensync-0.15/opensync'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/matt/dev/osync/libopensync-0.15'
make: *** [all] Error 2


Best wishes,
Matt