* Andreas Barth ([EMAIL PROTECTED]) [061127 19:10]:
> * Andreas Barth ([EMAIL PROTECTED]) [061127 06:22]:
> > basically, the only really required change is to replace libm17n*.so.*
> > by libm17n*.so* ib libm17n-0.install - but for safety reasons, one could
> > as well remove the libm17n*.so-line from libm17n-dev.install. The
> > following patch works well here.
>
> Julien Cristau reminded me on IRC that this patch would be a bad idea
> for the reason that it blocks upgrades to the next so-version of m17n.
>
> It should be rather different - the linked objects should link to
> ...so.0.
After more checking, the bug is somewhere else. The library dynamically
opens (in src/m17n-gui.c):
MSTRUCT_CALLOC (interface, MERROR_WIN);
interface->library = malloc (strlen (lib)
+ strlen (DLOPEN_SHLIB_EXT) + 1);
sprintf (interface->library, "%s%s", lib, DLOPEN_SHLIB_EXT);
which will of course fail unless the development package is there.
Now, I'm a bit lost - what is the correct behaviour? Also, this way of
binding seems a bit unsafe to me, or it at least leaves the area where I
know what happens inside.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
