Summary: | multisync-0.83_pre20050115 doesn't seem to support IrMC | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Preston <preston.newton> |
Component: | New packages | Assignee: | John Mylchreest (RETIRED) <johnm> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | centic, gad.kadosh, luisca, pda, pylon |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Preston
2005-01-21 15:42:54 UTC
Same here - use-flag for irmc activated, the files are installed in /usr/lib/multisync/, but not shown in the plugins-list when you're running multisync. Appearently the .so-files won't be created. If you do ln -s libirmc_sync.0.0.0 libirmc_sync.so ln -s libirmc_bluetooth.0.0.0 libirmc_bluetooth.so in /usr/lib/multisync and restart multisync, it also shows the IrMC Plugin. This also happens with the Opie plugin (multisync-0.83_pre20050115). $ ls /usr/lib/multisync [...] libopie_sync@ libopie_sync.0@ libopie_sync.0.0.0 libopie_sync.a libopie_sync.la [...] Adding the symlinks for libopie_sync.so and libopie_sync.0.so solves the problem. same behaviour here too same here with opie and irmc plugin. it looks like the links are created correctly, only the filenames for the shared objects are wrong. multisync seems to look for libPLUGINNAME_sync.so, but the opie and irmc plugins miss the ".so" in their filenames. after emerge: # cd /usr/lib/multisync # ll -rw-r--r-- 1 root root 39454 26. J same here with opie and irmc plugin. it looks like the links are created correctly, only the filenames for the shared objects are wrong. multisync seems to look for libPLUGINNAME_sync.so, but the opie and irmc plugins miss the ".so" in their filenames. after emerge: # cd /usr/lib/multisync # ll -rw-r--r-- 1 root root 39454 26. Jän 09:48 libbackup_plugin.a -rwxr-xr-x 1 root root 1718 26. Jän 09:48 libbackup_plugin.la lrwxrwxrwx 1 root root 25 26. Jän 09:48 libbackup_plugin.so -> libbackup_plugin.so.0.0.0 lrwxrwxrwx 1 root root 25 26. Jän 09:48 libbackup_plugin.so.0 -> libbackup_plugin.so.0.0.0 -rwxr-xr-x 1 root root 34452 26. Jän 09:48 libbackup_plugin.so.0.0.0 -rw-r--r-- 1 root root 40710 26. Jän 09:48 libevolution2_sync.a -rwxr-xr-x 1 root root 1842 26. Jän 09:48 libevolution2_sync.la -rwxr-xr-x 1 root root 32664 26. Jän 09:48 libevolution2_sync.so lrwxrwxrwx 1 root root 18 26. Jän 09:48 libirmc_sync -> libirmc_sync.0.0.0 lrwxrwxrwx 1 root root 18 26. Jän 09:48 libirmc_sync.0 -> libirmc_sync.0.0.0 -rwxr-xr-x 1 root root 98764 26. Jän 09:48 libirmc_sync.0.0.0 -rw-r--r-- 1 root root 124298 26. Jän 09:48 libirmc_sync.a -rwxr-xr-x 1 root root 1702 26. Jän 09:48 libirmc_sync.la -rwxr-xr-x 1 root root 1728 26. Jän 09:48 libldap_plugin.la lrwxrwxrwx 1 root root 23 26. Jän 09:48 libldap_plugin.so -> libldap_plugin.so.0.0.0 lrwxrwxrwx 1 root root 23 26. Jän 09:48 libldap_plugin.so.0 -> libldap_plugin.so.0.0.0 -rwxr-xr-x 1 root root 129940 26. Jän 09:48 libldap_plugin.so.0.0.0 lrwxrwxrwx 1 root root 18 26. Jän 09:48 libopie_sync -> libopie_sync.0.0.0 lrwxrwxrwx 1 root root 18 26. Jän 09:48 libopie_sync.0 -> libopie_sync.0.0.0 -rwxr-xr-x 1 root root 155476 26. Jän 09:48 libopie_sync.0.0.0 -rw-r--r-- 1 root root 198608 26. Jän 09:48 libopie_sync.a -rwxr-xr-x 1 root root 1719 26. Jän 09:48 libopie_sync.la -rw-r--r-- 1 root root 3326650 26. Jän 09:48 libsyncml_plugin.a -rwxr-xr-x 1 root root 1718 26. Jän 09:48 libsyncml_plugin.la lrwxrwxrwx 1 root root 25 26. Jän 09:48 libsyncml_plugin.so -> libsyncml_plugin.so.0.0.0 lrwxrwxrwx 1 root root 25 26. Jän 09:48 libsyncml_plugin.so.0 -> libsyncml_plugin.so.0.0.0 -rwxr-xr-x 1 root root 115556 26. Jän 09:48 libsyncml_plugin.so.0.0.0 I only created these symlinks to get it working: # ln -s libopie_sync.0.0.0 libopie_sync.so # ln -s libirmc_sync.0.0.0 libirmc_sync.so Now it finds the libPLUGIN_sync.so that multisync expects. on a side note, I had to change the syncpair files in ~/.multisync/*/ from evolution-sync to evolution2-sync, as I now use evolution 2 will this be fixed in portage? Bump Yep this will get fixed in the next release. It'll be after my holiday now im afraid. *** Bug 82422 has been marked as a duplicate of this bug. *** I havwe been looking into this and am unable to re-create this at all. I will be releasing a slightly updated ebuild shortly, if you would like to test. it will be -r1. please let me know what the outcome for you is. |