From: ntzrmtthihu777@... Date: 2017-03-10T00:28:00+00:00 Subject: [ruby-core:79986] [Ruby trunk Misc#13296] building ruby for windows always puts the version number into the ruby library, resulting in redundancy when using --with-soname Issue #13296 has been updated by Marty Plummer. Nobuyoshi Nakada wrote: > Yes, soname already includes major and minor version numbers, don't append them more. You seem to be misunderstanding what I'm talking about. Building ruby-2.4.0 on gentoo without using the --with-soname=ruby${ver} will always make the library have the following names: libruby.so, libruby.so.2.4.0, and libruby.so.2.4. Building 2.3.0 will result in libruby.so, libruby.so.2.3.0, and libruby-2.3. Do you see the problem here? without passing --with-soname=ruby${ver}, its impossible to install two or more versions of ruby system-wide, so it is an absolute must in order to use gentoo's slotted package architecture. Building ruby for windows/mingw using gentoo's crossdev tool uses the exact same ebuild, and the --with-soname argument cannot be removed from the mingw build without removing it from the native build. ---------------------------------------- Misc #13296: building ruby for windows always puts the version number into the ruby library, resulting in redundancy when using --with-soname https://bugs.ruby-lang.org/issues/13296#change-63407 * Author: Marty Plummer * Status: Rejected * Priority: Normal * Assignee: ---------------------------------------- Under gentoo the dev-lang/ruby-2.4.0.ebuild explicitly sets --program-suffix and --with-soname in order to facilitate multiple ruby version installations at the same time. Using crossdev for the x86_64-w64-mingw32 target, ruby's build system will set the final ruby libraries name to something like x64-msvcrt-${soname}${ver} which results in a final name of libx64-msvcrt-ruby24240.dll.a and so on. -- https://bugs.ruby-lang.org/ Unsubscribe: