On 7/8/2013 7:44 PM, Stanislav Sedov wrote:
Yeah, I attempted to just use the same patch from 2.0.0p195, and it did not apply cleanly. I removed the patch-lib_mkmf.rb and attempted to use the upstream mkmf.rb, but the same issue came up, .so's would get installed in the wrong location and loading the module would fail.On Jul 8, 2013, at 11:30 PM, Mike Carlson <[email protected]> wrote:The patch I supplied above is not working as I thought... The problem seems to be with the lib/mkmf.rb patch, its installing=20 compiled so' in an invalid location. For example, installing databases/rubygem-pg installs the pg_ext.so here:= /usr/local/lib/ruby/gems/2.0/gems/pg-0.15.1/lib/usr/local/lib/ruby/site_r= uby/2.0/amd64-freebsd9/pg_ext.so instead of: /usr/local/lib/ruby/gems/2.0/gems/pg-0.15.1/lib/pg_ext.soThat's weird. Did they change the internal logic of mkmf.rb? -- ST4096-RIPE
Our developer is requesting 2.0.0p247, so I did this in a quick attempt to bump the port version. This seems to be more complex than I thought and requires an expert set of eyes.
I can help test though. Mike C
smime.p7s
Description: S/MIME Cryptographic Signature
