Bug #3850: RUBY_SO_NAME inconsistency if ./configure --program-suffix is =
used on OpenBSD
http://redmine.ruby-lang.org/issues/show/3850

Author: Jeremy Evans
Status: Open, Priority: Normal
Category: build
ruby -v: ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-openbsd4.8]

If you use --program-suffix=3D19 when configuring ruby on OpenBSD, but do=
n't specify --with-soname=3Druby19, ruby will create an so file named rub=
y19.so.1.92 but leave RUBY_SO_NAME as ruby, leading to problems when link=
ing 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 offic=
ial ruby 1.9 port for OpenBSD is going to use --with-soname=3Druby19, but=
 this is a better default for people installing from source on OpenBSD.


----------------------------------------
http://redmine.ruby-lang.org
LS0tIGNvbmZpZ3VyZS5pbi5vcmlnCVNhdCBTZXAgMTggMTk6MDg6MDAgMjAx
MAorKysgY29uZmlndXJlLmluCVNhdCBTZXAgMTggMTk6NTg6MjcgMjAxMApA
QCAtMjExOSw3ICsyMTE5LDcgQEAKIAldLAogICAgIFtvcGVuYnNkKl0sIFsK
IAlTT0xJQlM9JyQoTElCUyknCi0JTElCUlVCWV9TTz0nbGliJChSVUJZX0lO
U1RBTExfTkFNRSkuc28uJChNQUpPUikuJ2BleHByICR7TUlOT1J9IFwqIDEw
ICsgJHtURUVOWX1gCisJTElCUlVCWV9TTz0nbGliJChSVUJZX1NPX05BTUUp
LnNvLiQoTUFKT1IpLidgZXhwciAke01JTk9SfSBcKiAxMCArICR7VEVFTll9
YAogCV0sCiAgICAgW3NvbGFyaXMqXSwgWwogCVNPTElCUz0nJChMSUJTKScK