https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112014-12-20T22:41:28ZRuby Issue Tracking SystemRuby master - Bug #10625: configure --with or --without-jemalloc failshttps://bugs.ruby-lang.org/issues/10625?journal_id=505332014-12-20T22:41:28Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><p>This is consist of 2 issues.</p>
<ul>
<li>
<code>with_jemalloc</code> is set to <code>yes</code> even if <code>--without-jemalloc</code> is given.</li>
<li>MacPorts jemalloc's <code>install_name</code> has the base name only, so its runtime library needs to be located in a system standard library path, or one of <code>DYLD_LIBRARY_PATH</code>.</li>
</ul> Ruby master - Bug #10625: configure --with or --without-jemalloc failshttps://bugs.ruby-lang.org/issues/10625?journal_id=505342014-12-20T23:35:50Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset r48907.</p>
<hr>
<p>configure.in: fix jemalloc option</p>
<ul>
<li>configure.in (jemalloc): fix option argument, should use<br>
<code>$withval</code> but not <code>yes</code> always. <a href="/issues/10625">[ruby-core:66994]</a> [Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: configure --with or --without-jemalloc fails (Closed)" href="https://bugs.ruby-lang.org/issues/10625">#10625</a>]</li>
<li>configure.in (jemalloc): defer adding the liner option to get<br>
rid of linking contest against jemalloc, so that it works<br>
without runtime dynamic load path.</li>
</ul> Ruby master - Bug #10625: configure --with or --without-jemalloc failshttps://bugs.ruby-lang.org/issues/10625?journal_id=505352014-12-21T00:30:22Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><p>Fixed the former bug, so <code>--without-jemalloc</code> should work.<br>
But the latter is caused by MacPorts jemalloc, it is just a workaround and you still need to set <code>DYLD_LIBRARY_PATH</code> to run built binaries.<br>
OS X <code>ld(1)</code> seems not to provide a way to override the runtime load path for linked libraries at link time.</p>