* [ruby-core:90744] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0
[not found] <redmine.issue-15470.20181227154626@ruby-lang.org>
@ 2018-12-27 15:46 ` rubylang
2018-12-27 17:53 ` [ruby-core:90747] " mseneadza
` (3 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: rubylang @ 2018-12-27 15:46 UTC (permalink / raw
To: ruby-core
Issue #15470 has been reported by kaspergrubbe (Kasper Grubbe).
----------------------------------------
Bug #15470: Getting Jemalloc to work with 2.6.0
https://bugs.ruby-lang.org/issues/15470
* Author: kaspergrubbe (Kasper Grubbe)
* Status: Open
* Priority: Normal
* 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
----------------------------------------
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:
~~~ ruby
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:
~~~ ruby
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?
---Files--------------------------------
2-5.log (62.8 KB)
2-6.log (71.1 KB)
rubyinstall.sh (1.97 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:90747] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0
[not found] <redmine.issue-15470.20181227154626@ruby-lang.org>
2018-12-27 15:46 ` [ruby-core:90744] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0 rubylang
@ 2018-12-27 17:53 ` mseneadza
2018-12-27 18:32 ` [ruby-core:90748] " rubylang
` (2 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: mseneadza @ 2018-12-27 17:53 UTC (permalink / raw
To: ruby-core
Issue #15470 has been updated by mseneadza (Michael Seneadza).
I ran into this the other day. Try:
~~~
irb(main):002:0> puts RbConfig::CONFIG['MAINLIBS']
-lpthread -ljemalloc -ldl -lobjc
~~~
----------------------------------------
Bug #15470: Getting Jemalloc to work with 2.6.0
https://bugs.ruby-lang.org/issues/15470#change-75923
* Author: kaspergrubbe (Kasper Grubbe)
* Status: Open
* Priority: Normal
* 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
----------------------------------------
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:
~~~ ruby
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:
~~~ ruby
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?
---Files--------------------------------
2-6.log (71.1 KB)
2-5.log (62.8 KB)
rubyinstall.sh (1.97 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:90748] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0
[not found] <redmine.issue-15470.20181227154626@ruby-lang.org>
2018-12-27 15:46 ` [ruby-core:90744] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0 rubylang
2018-12-27 17:53 ` [ruby-core:90747] " mseneadza
@ 2018-12-27 18:32 ` rubylang
2018-12-27 22:06 ` [ruby-core:90753] " shevegen
2018-12-28 0:51 ` [ruby-core:90759] [Ruby trunk Bug#15470][Rejected] " mame
4 siblings, 0 replies; 5+ messages in thread
From: rubylang @ 2018-12-27 18:32 UTC (permalink / raw
To: ruby-core
Issue #15470 has been updated by 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
~~~
----------------------------------------
Bug #15470: Getting Jemalloc to work with 2.6.0
https://bugs.ruby-lang.org/issues/15470#change-75924
* Author: kaspergrubbe (Kasper Grubbe)
* Status: Open
* Priority: Normal
* 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
----------------------------------------
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:
~~~ ruby
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:
~~~ ruby
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?
---Files--------------------------------
2-6.log (71.1 KB)
2-5.log (62.8 KB)
rubyinstall.sh (1.97 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:90753] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0
[not found] <redmine.issue-15470.20181227154626@ruby-lang.org>
` (2 preceding siblings ...)
2018-12-27 18:32 ` [ruby-core:90748] " rubylang
@ 2018-12-27 22:06 ` shevegen
2018-12-28 0:51 ` [ruby-core:90759] [Ruby trunk Bug#15470][Rejected] " mame
4 siblings, 0 replies; 5+ messages in thread
From: shevegen @ 2018-12-27 22:06 UTC (permalink / raw
To: ruby-core
Issue #15470 has been updated by shevegen (Robert A. Heiler).
Nice - I did not know about MAINLIBS in RbConfig::CONFIG before either.
----------------------------------------
Bug #15470: Getting Jemalloc to work with 2.6.0
https://bugs.ruby-lang.org/issues/15470#change-75926
* Author: kaspergrubbe (Kasper Grubbe)
* Status: Open
* Priority: Normal
* 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
----------------------------------------
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:
~~~ ruby
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:
~~~ ruby
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?
---Files--------------------------------
2-6.log (71.1 KB)
2-5.log (62.8 KB)
rubyinstall.sh (1.97 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:90759] [Ruby trunk Bug#15470][Rejected] Getting Jemalloc to work with 2.6.0
[not found] <redmine.issue-15470.20181227154626@ruby-lang.org>
` (3 preceding siblings ...)
2018-12-27 22:06 ` [ruby-core:90753] " shevegen
@ 2018-12-28 0:51 ` mame
4 siblings, 0 replies; 5+ messages in thread
From: mame @ 2018-12-28 0:51 UTC (permalink / raw
To: ruby-core
Issue #15470 has been updated by 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.
----------------------------------------
Bug #15470: Getting Jemalloc to work with 2.6.0
https://bugs.ruby-lang.org/issues/15470#change-75932
* Author: kaspergrubbe (Kasper Grubbe)
* Status: Rejected
* Priority: Normal
* 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
----------------------------------------
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:
~~~ ruby
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:
~~~ ruby
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?
---Files--------------------------------
2-6.log (71.1 KB)
2-5.log (62.8 KB)
rubyinstall.sh (1.97 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-12-28 0:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <redmine.issue-15470.20181227154626@ruby-lang.org>
2018-12-27 15:46 ` [ruby-core:90744] [Ruby trunk Bug#15470] Getting Jemalloc to work with 2.6.0 rubylang
2018-12-27 17:53 ` [ruby-core:90747] " mseneadza
2018-12-27 18:32 ` [ruby-core:90748] " rubylang
2018-12-27 22:06 ` [ruby-core:90753] " shevegen
2018-12-28 0:51 ` [ruby-core:90759] [Ruby trunk Bug#15470][Rejected] " mame
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).