[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35048] Re: Setting libpath for AIX

From: Perry Smith <pedzsan@...>
Date: 2011-02-02 17:48:37 UTC
List: ruby-core #35048
On Jan 28, 2011, at 8:25 PM, Perry Smith wrote:

> 
> On Jan 28, 2011, at 7:17 PM, Yutaka Kanemoto wrote:
> 
>> Hi,
>> 
>> If you add -L. when you link a library/executable, the linker add .
>> (current dir) to libpath by default.
>> We need to avoid this not to load unexpected library for security
>> reason. That is the reason why now we use -blibpath to explicitly
>> decide the libpath.
>> 
>> I think it is hard to eliminate "-L.", "-L../.." from current build process.
>> We need to look for another way to add such path to libpath.
>> If you have any nice idea, please let me know.
> 
> I believe what you are saying is currently, the link lines often have -L .
> and -L .. so you want to avoid adding . and .. to the internal libpath of
> the shared library or executable.
> 
> Curiously, -blibpath is not specified in the places that -L . and -L ..
> is being passed.  libpath is specified only in three places in the build
> I just did.  The link of miniruby, libruby.so, and ruby
> 
> There are other ways to avoid -L . and -L .. if that really is needed but
> I don't see how that concern relates to the link commands that
> specify libpath.
> 
> The link of these three specify:
> 
> -Wl,-blibpath:/usr/local//rvm/rubies/ruby-1.9.1-p378/lib:/usr/lib:/lib
> 
> I'm suggesting replace that with:
> 
> -L /usr/local//rvm/rubies/ruby-1.9.1-p378/lib

I never heard a reply.  The current system is not working.  It has to change somehow.

Should I open a bug report on this?

Thank you,
Perry


In This Thread