http://bugs.meego.com/show_bug.cgi?id=10266
--- Comment #10 from pohly <[email protected]> 2010-12-22 12:24:46 PST --- (In reply to comment #9) > (In reply to comment #8) > > Now that you mention it explicitly I realize that the error message is > > indeed > > harmless. > > What, the syncecal message, which is completely different from the edataserver > message in the original post? Clearly not the same problem... The initial report was a bit misleading (the description did not mention syncecal.so), but it did mention libecal.so in the "actual outcome" part. I think it is the same problem. > > The syncecal.so backend is not needed on the N900. I'm not sure why > > it is enabled at all in the N900 build. It seems that libecal is still > > available in the system for whatever reason, although it is no longer used. > > An > > explicit --disable-ecal would make SyncEvolution a bit smaller and avoid the > > error message, but that's really minor. > > My packages are configured with --disable-ecal, and always have been. If > syncecal is still built, that's probably not because of my configuration > options... It should get built, but without any real code. What it contains then is just some check that recognizes "type=Evolution Calendar" and leads to an obvious "backend disable during compilation" kind of error. Can you do a "objdump -T" on syncecal.so to check what it contains and needs? -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
