+- 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: Bearbin's Automated Builds (/thread-538.html)
RE: Bearbin's Automated Builds - tonibm19 - 01-25-2015
Ashhh, that bad because most people do actually use debian 7 (I think)
RE: Bearbin's Automated Builds - bearbin - 01-25-2015
I know. Gcc 4.8 or above is not available for it though. I'm going to fix it but it will need a reinstall of the OS.
I think I'll also move over to a dedicated server when I reinstall too, but it might take a week or 2.
RE: Bearbin's Automated Builds - Seadragon91 - 01-25-2015
Whats about upgrading it?
Code:
1. Edit /etc/apt/sources.list by replacing "wheezy" with "jessie"
2. Run apt-get update && apt-get upgrade
3. Then apt-get dist-upgradeRE: Bearbin's Automated Builds - tonibm19 - 01-25-2015
I read about that. It didnt work for me thought.
Anyway, most people wont update until their host does it.
RE: Bearbin's Automated Builds - bearbin - 01-25-2015
The problem with that is that it brings in the newer version of Glibc, which means that you can't run the programs you compile on the newer os on the older one.
RE: Bearbin's Automated Builds - worktycho - 01-25-2015
You might want to try and make a build that uses clang, libc++ and a alternative libc, linked staticly. That would avoid any dependencies on libraries already on the system.
RE: Bearbin's Automated Builds - bearbin - 01-26-2015
Yeah, I should do that. It depends on when I can get a new dedi though.
RE: Bearbin's Automated Builds - xoft - 01-26-2015
I'm not so sure about this, in relation to LuaRocks. Those work by effectively merging the main executable and the compiled rocks; and it may cause problems if different CRTs are used.
RE: Bearbin's Automated Builds - worktycho - 01-26-2015
It wouldn't be the main build. For one thing thing it would significantly increase executable size. It would also have the potential to add a couple of MB to memory usage due to increased executable size. It probably wouldn't be what you want to use if you need luaRocks, but their isn't really an option to use luaRocks that works unless you set-up a really complex build enviroment. It would probably be easier to cross-compile from arm to x86 debian 7 than x86 debian 8 to x86 debian 7. It would definitely need to use libc++ and clang but building against a non-system glibc is really difficult unless you're cross compiling.
RE: Bearbin's Automated Builds - bearbin - 02-16-2015
The armhf build is now fixed.
I can't work out why the x86 build suddenly broke on the 27th though, could anybody help?
Log: http://builds.cuberite.org/job/MCServer%20Linux%20x86/391/console