Home → Geekbench →

Running Geekbench on CentOS 7

• Edit

jfettig

14 Oct, 2014 06:22 PM

When I try to run geekbench on CentOS7, I get the following:

[Geekbench-3.2.2-Linux]$ ./geekbench
[Geekbench-3.2.2-Linux]$ ./geekbench_x86_32
Segmentation fault (core dumped)

It seems I cannot run either executable. Any ideas?

1. Support Staff 1 Posted by John on 15 Oct, 2014 03:22 AM

   

   Hi John,

   Thank you for your message. Can you run the geekbench_x86_64 executable?

   Thanks,
   John

   • Edit

2. 2 Posted by jfettig on 15 Oct, 2014 01:00 PM

   

   Hi John,

   Yes, I can run the x86_64 executable but it just prints the "tryout mode" message and exits, regardless of options passed, presumably because only 32 bit runs are allowed in tryout mode.

   • Edit

3. Support Staff 3 Posted by John on 02 Dec, 2014 07:01 AM

   

   Hi John,

   I apologize for the delay in getting back to you. You'll need to install 32-bit libraries in order for Geekbench 3 to work on 64-bit CentOS systems.

   sudo yum install libc6.i386 libstdc++6.i386
   

   Let me know if that solves the issue you encountered.

   Thanks,
   John

   • Edit

4. 4 Posted by jfettig on 02 Dec, 2014 07:43 PM

   

   John,

   I presume you mean packages:

   glibc.i686
   libstdc++.i686

   If so, I already have those.

   John

   • image001.jpg 332 Bytes
   • Edit

5. 5 Posted by ShawnC on 05 Dec, 2014 10:33 PM

   

   seems this worked for me:

   sudo yum install glibc.i686

   • Edit

6. 6 Posted by ShawnC on 05 Dec, 2014 10:43 PM

   

   actually, needed 3:

   sudo yum install glibc.i686
   sudo yum install libstdc++
   sudo yum install libstdc++.i686

   • Edit

7. 7 Posted by jfettig on 08 Dec, 2014 02:08 PM

   

   I have all of these packages:

   Package glibc-2.17-55.el7_0.1.i686 already installed and latest version
   Package libstdc++-4.8.2-16.2.el7_0.x86_64 already installed and latest version
   Package libstdc++-4.8.2-16.2.el7_0.i686 already installed and latest version

   In any case, I am not really interested in running the 32 bit version anymore as we bought a pro license. It is troublesome that the default geekbench program exits without any message, which I presume is related to the 32 bit version segfaulting. The backtrace is useless, too:

   #0 0x081088fa in ?? ()
   #1 0x081080c1 in ?? ()
   #2 0x0806aeab in ?? ()
   #3 0x08068e08 in ?? ()
   #4 0x08068c75 in ?? ()
   #5 0x0805d3fb in ?? ()
   #6 0x08052dae in ?? ()
   #7 0x0805b129 in ?? ()
   #8 0xf7cb3933 in __libc_start_main () from /lib/libc.so.6
   #9 0x0804db41 in ?? ()

   • image001.jpg 332 Bytes
   • Edit

8. Support Staff 8 Posted by John on 14 Dec, 2014 04:03 PM

   

   Interesting! While we don't officially support Geekbench 3 on CentOS we'll try and schedule time to see if we can figure out what's going on with 32-bit Geekbench on 64-bit CentOS.

   Thanks,
   John

   • Edit

9. 9 Posted by Fortinuex on 07 Jan, 2015 02:56 PM

   

   CentOS is linux based John if I am correct. Maybe run the registering line of code in terminal to unlock it first.

   • Edit

10. 10 Posted by robert on 17 Jul, 2015 02:12 AM

    

    ShawnC has it right. I had tremendous problems trying to find the right packages to run 32 bit binaries on CentOS 6.5 64bit. But following his instructions, Geekbench 2.4.3 binaries worked.

    I installed the packages in the following order on a fresh OS install.

    sudo yum install glibc.i686 (success)
    sudo yum install libstdc++ (gave me 'already installed' message)
    sudo yum install libstdc++.i686 (success)

    Thanks!

    • Edit

11. 11 Posted by GoEz on 27 Aug, 2015 06:41 PM

    

    Hi Robert,

    Wondering if you can help me out since I'm trying to test with CentOS 7 64x with the available ARM Geekbench.

    I keep getting "No package found" for each of the packages listed above.

    I'm going to try switching to another HD soon to test on Fedora if I can't get this figured out.

    Thanks

    • Edit

12. 12 Posted by GoEz on 27 Aug, 2015 08:18 PM

    

    Scratch my last comment, I'm dealing with ARM! :P

    Made my own thread, sorry!

    • Edit

13. 13 Posted by Robert on 27 Aug, 2015 09:31 PM

    

    This solution only works on an Intel or AMD CPU. Sorry, does not work for ARM cpu.

    If you see x86, 386, 686, etc, you can be sure it's not going to run.

    • Edit