How I got Cuberite to compile on Centos 6.7

How I got Cuberite to compile on Centos 6.7 - Printable Version

+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Discussion (https://forum.cuberite.org/forum-5.html)
+--- Thread: How I got Cuberite to compile on Centos 6.7 (/thread-2242.html)

How I got Cuberite to compile on Centos 6.7 - chrobione - 12-10-2015

Hello All,

I am not sure where to put these instructions so I will put them here for now.

To get cuberite to install on Centos 6.7 I did the following:

First we need to install the devtools-2 repo by running this command:

Code:
sudo wget http://people.centos.org/tru/devtools-2/devtools-2.repo -O /etc/yum.repos.d/devtools-2.repo

Next we to actually installed devtools (including c++):

Code:
yum install devtoolset-2-gcc devtoolset-2-binutils devtoolset-2-gcc-c++

Then we enter the devtoolset SCL command for the build enviroment:

Code:
scl enable devtoolset-2 bash

If no errors were encounter there you should be able to compile with centos 6.7 by doing either of the following commands:

Code:
sh -c "$(wget -O - https://raw.githubusercontent.com/cuberite/cuberite/master/compile.sh)"

Or if you already have the cuberite download:

Code:
cd cuberite

./compile.sh

I did see warnings but it seems to work.

Hope this helps...

RE: How I got Cuberite to compile on Centos 6.7 - LogicParrot - 12-11-2015

Hello, isn't yum install clang git cmake make sufficient? If not, I'll need to update compile.sh

RE: How I got Cuberite to compile on Centos 6.7 - Zee1234 - 12-11-2015

(12-11-2015, 05:59 AM)Safwat Wrote: Hello, isn't yum install clang git cmake make sufficient? If not, I'll need to update compile.sh

Not sure about 6.7, but I know I had to install the DeveloperTools on CentOS 7 as gcc (gcc++?) wasn't available outside of it/had a different name/wouldn't install with yum install gcc nor yum install gcc++ for some other reason.

Edit:

Code:
yum groupinstall "Development Tools"

was the command.

RE: How I got Cuberite to compile on Centos 6.7 - chrobione - 12-11-2015

(12-11-2015, 05:59 AM)Safwat Wrote: Hello, isn't yum install clang git cmake make sufficient? If not, I'll need to update compile.sh

Yum install clang returned no clang package.

(12-11-2015, 07:41 AM)Zee1234 Wrote: Not sure about 6.7, but I know I had to install the DeveloperTools on CentOS 7 as gcc (gcc++?) wasn't available outside of it/had a different name/wouldn't install with yum install gcc nor yum install gcc++ for some other reason.

Edit:
Code:
yum groupinstall "Development Tools"
was the command.

I did not try this command yet, I will post back in a few to let you know if that works for 6.7 as

RE: How I got Cuberite to compile on Centos 6.7 - chrobione - 12-11-2015

Code:
yum groupinstall "Developement Tools"

Only installed 4.4.7 which is still to old.. So it seems instructions are different between CentOS versions.

chrobione

RE: How I got Cuberite to compile on Centos 6.7 - LogicParrot - 12-12-2015

Apparently it's called gcc-c++.

I might need to tweak compile.sh a bit.

RE: How I got Cuberite to compile on Centos 6.7 - chrobione - 12-12-2015

(12-12-2015, 03:10 AM)Safwat Wrote: Apparently it's called gcc-c++.

I'll might need to tweak compile.sh a bit.

So I ran the command as shown in the link to install the gcc-c++ on my CentOS 6.7. The intresting thing is that It was already installed from the Development Tools, yet it was still the wrong version for my version of CentOS.

[root@localhost ~]# sudo yum install gcc-c++
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: centos.mirror.nac.net
* extras: mirror.team-cymru.org
* updates: mirror.tocici.com

base | 3.7 kB 00:00
extras | 3.4 kB 00:00
updates | 3.4 kB 00:00
Package gcc-c++-4.4.7-16.el6.x86_64 already installed and latest version
Nothing to do
[/code]

By the way this is looking to me:

If you use

Code:
sudo yum groupinstall "Development Tools"

for CentOS 7 you should be good to go.

With 6.7 the instructions at the top still seem the only way to get it to compile with warnings.

--chrobi