Bug #15470: Getting Jemalloc to work with 2.6.0

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux]
• Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN

[kaspergrubbe (Kasper Grubbe)]

I have a install script that installs all build requirements for Ruby together with libjemalloc, it then configures Ruby with the --with-jemalloc flag, they were all run on Debian 9 which installs jemalloc 3.6.0 from the Debian repositories.

When I run my script with Ruby 2.5, I get the following output from irb:

puts RbConfig::CONFIG['LIBS']
# -lpthread -ljemalloc -ldl -lcrypt -lm

However, if I build Ruby 2.6 in the exact same way, I do not see -ljemalloc flag:

puts RbConfig::CONFIG['LIBS']
# -lm

I've attached the output from the configure and make steps to this.

Did something change? Or do I need to change the way I do jemalloc detection with Ruby 2.6?

[mseneadza (Michael Seneadza)]

I ran into this the other day. Try:

irb(main):002:0> puts RbConfig::CONFIG['MAINLIBS']
-lpthread -ljemalloc -ldl -lobjc

[kaspergrubbe (Kasper Grubbe)]

mseneadza (Michael Seneadza) wrote:

I ran into this the other day. Try:

irb(main):002:0> puts RbConfig::CONFIG['MAINLIBS']
-lpthread -ljemalloc -ldl -lobjc

Oh that did work for me too!

irb(main):001:0> puts RbConfig::CONFIG['MAINLIBS']
-lz -lpthread -lrt -lrt -ljemalloc -ldl -lcrypt -lm

[shevegen (Robert A. Heiler)]

Nice - I did not know about MAINLIBS in RbConfig::CONFIG before either.

[mame (Yusuke Endoh)]

• Status changed from Open to Rejected

So, we can close this ticket, right? Let me know if you still have any trouble.