Hi, guys,
i've just switch from packaged geany to svn. My --prefix=$HOME and everything builds and installs fine. When i start up now i'm seeing:
20:13:02: This is Geany 0.21 (svn >= r5864). 20:13:02: The plugin "/usr/lib/geany/classbuilder.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanydoc.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanygendoc.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanygdb.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanyvc.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/splitwindow.so" is not binary compatible with this release of Geany - please recompile it. ...
note the /usr/lib, though it's compiled with --prefix=$HOME.
i've verified that the running binary is the one i installed:
stephan@tiny:~/cvs/geany$ ps -ef | grep geany stephan 2275 1 3 20:13 ? 00:00:05 /home/stephan/bin/geany
What's the proper way for me to fix/work around that (i don't mind rebuilding if needed).
On Thu, 30 Jun 2011 20:16:16 +0200 Stephan Beal sgbeal@googlemail.com wrote:
Hi, guys,
i've just switch from packaged geany to svn. My --prefix=$HOME and everything builds and installs fine. When i start up now i'm seeing:
20:13:02: This is Geany 0.21 (svn >= r5864). 20:13:02: The plugin "/usr/lib/geany/classbuilder.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanydoc.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanygendoc.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanygdb.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/geanyvc.so" is not binary compatible with this release of Geany - please recompile it. 20:13:02: The plugin "/usr/lib/geany/splitwindow.so" is not binary compatible with this release of Geany - please recompile it. ...
note the /usr/lib, though it's compiled with --prefix=$HOME.
i've verified that the running binary is the one i installed:
stephan@tiny:~/cvs/geany$ ps -ef | grep geany stephan 2275 1 3 20:13 ? 00:00:05 /home/stephan/bin/geany
What's the proper way for me to fix/work around that (i don't mind rebuilding if needed).
Geany is storing the plugins which has been loaded inside geany.conf with full path. If you open that file, you could remove them.
Cheers, Frank
On 06/30/11 11:16, Stephan Beal wrote:
What's the proper way for me to fix/work around that (i don't mind rebuilding if needed).
I think this is the same issue as the bug I reported[1] a while ago, except I was using the same version in two locations so it didn't give such error messages.
Frank's workaround should do the trick until it gets fixed. Or go into the older version and de-active all the plugins, then go into the newer version (or vice versa) and re-activate them.
[1] https://sourceforge.net/tracker/?func=detail&aid=3314501&group_id=15...
Cheers, Matthew Brush
On Thu, Jun 30, 2011 at 8:53 PM, Matthew Brush mbrush@codebrainz.ca wrote:
Frank's workaround should do the trick until it gets fixed. Or go into the older version and de-active all the plugins, then go into the newer version (or vice versa) and re-activate them.
That fixed it just fine :). i don't consider this a bug, but i guess it could be if you're using two versions (or same version, two copies...).
On 1 July 2011 05:41, Stephan Beal sgbeal@googlemail.com wrote:
On Thu, Jun 30, 2011 at 8:53 PM, Matthew Brush mbrush@codebrainz.ca wrote:
Frank's workaround should do the trick until it gets fixed. Or go into the older version and de-active all the plugins, then go into the newer version (or vice versa) and re-activate them.
That fixed it just fine :). i don't consider this a bug, but i guess it could be if you're using two versions (or same version, two copies...).
You need to use different config files with -c in that case.
Thats what I do to keep my dev version separate from the system version in case it craps on the config.
Cheers Lex
-- ----- stephan beal http://wanderinghorse.net/home/stephan/
Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Fri, 1 Jul 2011 11:08:53 +1000 Lex Trotman elextr@gmail.com wrote:
On 1 July 2011 05:41, Stephan Beal sgbeal@googlemail.com wrote:
On Thu, Jun 30, 2011 at 8:53 PM, Matthew Brush mbrush@codebrainz.ca wrote:
Frank's workaround should do the trick until it gets fixed. Or go into the older version and de-active all the plugins, then go into the newer version (or vice versa) and re-activate them.
That fixed it just fine :). i don't consider this a bug, but i guess it could be if you're using two versions (or same version, two copies...).
You need to use different config files with -c in that case.
Yes. In combination with setting up an alias you can choose between by just using a different command.
Cheers, Frank