buffer8848 / gperftools

Automatically exported from code.google.com/p/gperftools

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

tcmalloc -- Broke Ruby EE Install on ARM

GoogleCodeExporter opened this issue · comments

What steps will reproduce the problem?
1. I was trying to install Ruby Enterprise Edition.
2. I was using the tarball to compile from source.
3. I was using the standard installer, which exited [1] citing tcmalloc

What is the expected output? What do you see instead?
On a normal AMD64 or ia386, it compiles every time.  This time, it exited
the install. 

What version of the product are you using? On what operating system?
Ubuntu for the ARM architecture running on a Sheeva Plug Dev kit from
Globalscale technologies.

Please provide any additional information below.
I first reported this to the Ruby EE mailing list.  The workaround seemed
to work.  I haven't tested it, but it did compile.  I'll let you now how it
behaves.

http://groups.google.com/group/emm-ruby/browse_thread/thread/95e4c279165bc599?hl
=en

h@m@nn_p@ul@y@hoo Dot Com

Original issue reported on code.google.com by hamann_p...@yahoo.com on 22 Aug 2009 at 4:02

Original comment by `` on 18 Jan 2012 at 9:38

tcmalloc isn't ported to ARM, so it won't compile for you (the error was 
because it
wsa trying to use x86 assembly on an arm chip).  If you are up for helping port
tcmalloc to ARM (see issue 113), that would be great!

Original comment by csilv...@gmail.com on 22 Aug 2009 at 4:07

  • Changed state: Duplicate
  • Added labels: Priority-Medium, Type-Defect
Also -- it looks like I don't have permission to post to the ruby mailing list 
-- you
might want to suggest to them that they make --no-tcmalloc the default for all
systems except i386, x86_64, and PPC.  Those are the only architectures 
tcmalloc has
currently been ported to.

Original comment by csilv...@gmail.com on 22 Aug 2009 at 4:10

Thanks.  I will let them know that they should specify --no-tcmalloc as the 
default
for all the "non-usual suspects".  I would love to help port to ARM, but it is 
way
beyond me.

--Thanks

Original comment by hamann_p...@yahoo.com on 22 Aug 2009 at 4:23