-
-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry Pi Crash - "pure virtual method called" #1976
Comments
You can try one of my daily builds: https://minefight.org/ftp/MCServer/ Maybe a too old or new libc library. |
Which LIBC version does MCServer require? |
For the buildserver builds, something like 2.13? |
Report 1 uses |
Sorry, actually should be libc 2.19 for x86/64 ARM may be different, because of the differences with cross-compilation. |
Was able to reproduce the issue on my bananapi with jenkins armhf build 153. I'm currently building it from source natively on my bananapi as well. Will post an update when that's finished. |
Jenkins build 154 crashes as well with the same issue. Native build on my bananapi does NOT crash and works fine. Looks like it's an issue with cross compilation. |
Yup, none of the jenkins armhf builds work, however the builds by @falkseidl work fine.
libc* versions: |
I had the same problem on my banana pi and cubieboard. Now I have a cronjob that is starting the compiling every night at 3 clock (CET) on the cubieboard. |
I'm going to try and investigate the problem, perhaps I will update the cross-compiler to the latest version. |
I've just tried build 155 from the buildserver, and it starts up alright on my RasPi. |
How about providing PI users (or all users)with a "deploy" script, which clones and compiles automatically? It could also serve as an update script. I could give it a shot. |
You could. But it requires the installation of a compiler as well, which people probably wouldn't want. I'm re-doing the cross-compilation setup so it should work better with the newer OSes ATM, but IDK if it will work. |
Alright. In the meantime, here's a quick workaround for Pi users, just run this script and it'll download and compile everything. |
(About the name, I think we agreed to name the organisation Cuberite, as an umbrella for MCS, ProtoProxy, AnvilStats, etc.) |
OK, I have set up the cross-compilation again and tested on my pi, it works. Could somebody else with a pi test to confirm the builserver builds now work again. |
How about we do this? |
Still doesn't work on my BananaPi unfortunately. This is the build I tested: http://builds.cuberite.org/job/MCServer%20Linux%20armhf/3/ |
Hm. What's your kernel version? |
The new builds work on my Pi, too. Tested build 3. |
3.4.104+ armv7l GNU/Linux which explains a lot, since the RaspberryPi is armv6. Didn't realize that the BananaPi had a different architecture. Nevermind then. Though that means the mentioned deploy script will certainly be needed, unless you are planning on providing precompiled binaries for every architectural *Pi flavour out there. |
The piv2 is armv7 as well. |
So, the issue was running armV6 on ArmV7 hardware? |
Probably, but the Pi2 supports running ARMv6 code so that's why it works and the others dont AFAIK. |
But artur9010@forums reported the issue with Pi2 |
I think a recent firmware update to the pi also broke old software, after I recreated the cross-compile build it worked fine on the pi2s. |
So, closed? |
I think so. Everything works fine on an actual pi now, it's just the pi-likes that have the issue. And your self-compile script helps for those. |
Yes, remember to put it somewhere more accessible such as the homepage some day. |
Unfortunately, this does not work as it should :( |
@artur9010, What do you mean in particular? |
Build 24 (http://builds.cuberite.org/job/MCServer%20Linux%20armhf/24/)
|
Using arch linux is the most likely issue. Please compile the server yourself. @SafwatHalaby made a script that makes it easy. |
It's works. |
Yay, my script works :P |
This was reported by 2 different users, MCServer on Raspberry Pi crashes on startup.
Report 1 (libc 2.21):
Report 2:
The text was updated successfully, but these errors were encountered: