MR2 broke plugin during C extension require

Dan Rathbun

Hey Dan. I ran the script and it didn't help.

...

is always 40755 (octal I believe?) for the directories, before and after running your script.

Well sorry. As I did say it wasn't tested.

draftomatic

@dan rathbun said:

As I did say it wasn't tested.

Oh, I think it did was it was supposed to, except that maybe the chmod call didn't do anything. Not sure, but it did recurse the folders okay, so thanks for that! =D

I may get a coworker to help me out with this later in the week since she knows more about chmod and permissions.

thomthom

Isn't it easier to just test on another machine? One with a clean SU installation. Then you can find out if it's a local issue or not.

draftomatic

@thomthom said:

Isn't it easier to just test on another machine? One with a clean SU installation. Then you can find out if it's a local issue or not.

I have tried 4 machines with fresh installations - 1 XP, 2 Vista, 1 Win7.

The two Vistas have the problem. The others don't.

draftomatic

Here's the troublesome .so file. Just rename it with a .so extension (Sketchucation wouldn't let me upload as .so) Although it might depend on others in the Ruby installation.

This came straight from:

Ruby 1.8.6 p287 One-Click Installer: http://rubyforge.org/frs/download.php/47082/ruby186-27_rc2.exe

openssl.txt

draftomatic

FYI, all I did with my plugin is I packaged most of that Ruby installation in the above post with my plugin. I tried to trim most of the fat as there are source files etc. in there. Probably still left a huge amount in that doesn't need to be...

Edit: I know I've made several post about this before, but I tried to do the same thing on Mac and I could never get a 1.8.5 that would work (I even tried compiling it but every version I could find after scouring the internet was missing the thread.so standard C extension. A sad story... we still don't have Mac support because of this >.< ).

So anyway if you want to reproduce the error, just drop that installation into your \Plugins\Foo folder and try requiring openssl.so on Vista. As always you may want to adjust your $LOAD_PATH variable.

thomthom

I had no problems loading the openssl.so file you posted. (Win7 64bit)

thomthom

@draftomatic said:

FYI, all I did with my plugin is I packaged most of that Ruby installation in the above post with my plugin. I tried to trim most of the fat as there are source files etc. in there. Probably still left a huge amount in that doesn't need to be...

Note that it can cause incompatible clashes. For instance if you bundle set.rb it will conflict with the Set class that ships with SU. And if some of the files you bundle modifies the core classes it could also cause clashes as SU ships with slightly modified core classes.

thomthom

@draftomatic said:

@thomthom said:

Isn't it easier to just test on another machine? One with a clean SU installation. Then you can find out if it's a local issue or not.

I have tried 4 machines with fresh installations - 1 XP, 2 Vista, 1 Win7.

The two Vistas have the problem. The others don't.

Ah - did not notice this post... Don't have Vista at hand for testing...

draftomatic

@thomthom said:

Ah - did not notice this post... Don't have Vista at hand for testing...

I was waiting for you to pick up on this lol... it's Vista!!!

@thomthom said:

Note that it can cause incompatible clashes. For instance if you bundle set.rb it will conflict with the Set class that ships with SU. And if some of the files you bundle modifies the core classes it could also cause clashes as SU ships with slightly modified core classes.

That's a good point... What would you recommend? Should I try to eliminate those that clash from what I'm including with my plugin?

thomthom

@draftomatic said:

That's a good point... What would you recommend? Should I try to eliminate those that clash from what I'm including with my plugin?

I'd recommend that you check carefully what files you bundle. Since it's a shared environment you want to avoid potential clashes. Remove any file you don't need. Check the ones you add if they modify existing methods. And beware that Set.rb will cause incompatible modifications to the Set class.