On Di, 2011-08-23 at 09:33 +0000, Woodhouse, David wrote:
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
This is the rpath:
0x000000000000000f (RPATH) Library rpath:
It does contain the install directory, but so is the build directory,
and ldd did find the right library:
$ ldd /home/pohly/work/activesyncd/eas-daemon/libeas/.libs/libeas.so | grep account
No idea why ld doesn't. Shrug.
I'm surprised that libtool would put that rpath into the
during the initial build; did you configure with --enable-fast-install?
Personally I always install using symlinks (the trick documented at
) so I never get
stale libraries installed or have to remember to run 'make install'
after building, so I didn't see this problem.
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.