Backport #3850: RUBY_SO_NAME inconsistency if ./configure --program-suffix is used on OpenBSD

• Status: Closed
• Assignee: yugui (Yuki Sonoda)

[jeremyevans0 (Jeremy Evans)]

=begin
If you use --program-suffix=19 when configuring ruby on OpenBSD, but don't specify --with-soname=ruby19, ruby will create an so file named ruby19.so.1.92 but leave RUBY_SO_NAME as ruby, leading to problems when linking when building extensions with extconf/mkmf, since it will use -lruby instead of -lruby19.

It looks like the change to separate the soname from the program name was intentional (r23368), but it was not done for OpenBSD, since the actual created soname uses RUBY_INSTALL_NAME instead of RUBY_SO_NAME. The official ruby 1.9 port for OpenBSD is going to use --with-soname=ruby19, but this is a better default for people installing from source on OpenBSD.
=end

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed
• % Done changed from 0 to 100

=begin
This issue was solved with changeset r29298.
Jeremy, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end

[nobu (Nobuyoshi Nakada)]

• Status changed from Closed to Assigned
• Assignee set to yugui (Yuki Sonoda)

=begin

=end

[yugui (Yuki Sonoda)]

• Status changed from Assigned to Closed

=begin
This issue was solved with changeset r29563.
Jeremy, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end