On Tue, 2011-08-23 at 08:49 +0200, Patrick Ohly wrote: > Found it. stracing the final ld invocation shows that it looks at an old > libeasaccount.so.0 in my /tmp/activesyncd install dir. Wiping that out > first avoided the issue. > > I still don't know why ld considers those old libs at all. Does setting > the rpath have that effect? That is the only reference > to /tmp/activesyncd/lib.
It's more likely to be the rpath in libeas.so itself, rather than on the command line. I'm surprised that libtool would put that rpath into the libraries during the initial build; did you configure with --enable-fast-install? Personally I always install using symlinks (the trick documented at http://www.advogato.org/person/dwmw2/diary/219.html ) so I never get stale libraries installed or have to remember to run 'make install' after building, so I didn't see this problem. -- Sent with MeeGo's ActiveSync support. David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
