Re: [Evolution-hackers] installing evolution-data-server fails on a FHS compliant system

Le dimanche 22 mai 2005 à 18:41 -0400, Rodney Dawes a écrit :
> On Sun, 2005-05-22 at 19:35 +0200, Christian Krause wrote: 
> > Hello JP,
> > 
> > > > When installing evolution-data-server 1.2.x on a system which has a
> > > > FHS [1] compliant directory structure the evolution-data-server-1.2
> > > > binary is copied to a wrong place so that the evolution doesn't find
> > > > it. This results in a not-working evolution.
> > > 
> > > Why would this cause evolution not to find it?  The .server should still
> > > point to the right location.
> > 
> > No, it doesn't.
> This is a problem with the build environment. You need to re-run
> libtoolize. The for e-d-s is correct. The problem is
> that libtool is creating a directory with the same name as the
> binary is being copied to. This means that when the binary is
> copied, it gets placed in the versioned directory, without the
> version as part of the binary's filename itself.

This is not a problem with libtool and running libtoolize won't fix the
problem. I hit the problem on Mandriva cooker when we switched to eds
2.2.2, for the exact same reason Christian explained, because evolution
data server main process filename is the same as evolution library
directory name (evolution-data-server-1.2), so when libtool installs the
server executable, it find a directory with target name and will drop
executable it it, without renaming it. The only way to fix this was to
change to point to the new executable location.

But I've just realized changing executable filename will change process
name and will break evolution --force-shutdown (which is broken ATM
because it is still trying to kill evolution-data-server-1.0, as I
realized 30s ago while checking code..).

Frederic Crozat <fcrozat mandriva com>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]