Re: [SyncEvolution] failed to compile 1.3

On Thu, 2012-09-13 at 16:36 +0200, Vladimir Elisseev wrote: I see roughly where it crashes, but I have no idea why. It looks like a boost::signals2 internal boost::shared_ptr is empty at a time when boost::signals2 expects it to be set. SyncEvolution is careful to work with real singletons her (instances initialized in a function before returning a pointer to them), so it is not a problem of using a global instance which has not been initialized yet at a time when another global instance constructor tries to use it - I hope Boost itself is not making that mistake. Did the version of Boost perhaps change since the last time that you built SyncEvolution? Can you double-check by recompiling SyncEvolution 1.2.99.4 with the current set of system libraries? Alternatively (or in addition), can you compile with "-O0 -g" and produce another stack backtrace? It might be a bit more informative. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.