Page 1 of 1

Syscall ABI mismatch

Posted: Mon Jun 25, 2012 3:53 pm UTC
by JOURNEYMAN

After git pull and make, I get the following error.

recursive error 'Syscall ABI mismatch' after: Syscall ABI mismatch

How to fix? :confused: What does this even mean?


Re: Syscall ABI mismatch

Posted: Tue Jun 26, 2012 12:27 am UTC
by Anomalous

It'll go away soon. For now, stick with 6f8450a3f6e73832d52060a6ce5e44b08b587fee or set sv_pure=0 (and test locally).


Re: Syscall ABI mismatch

Posted: Tue Jun 26, 2012 5:25 am UTC
by Ishq

What it means is that there have been compatibility breaking changes in master that prevent you from playing on older servers. It'll disappear when Alpha 5 is released.


Re: Syscall ABI mismatch

Posted: Tue Jun 26, 2012 12:12 pm UTC
by MoD
Anomalous wrote:

It'll go away soon. For now, stick with 6f8450a3f6e73832d52060a6ce5e44b08b587fee or set sv_pure=0 (and test locally).

I tried to add 'sv_pure' to cfg files as well as environment variables, but the error still appears. Could you please explain how to set it correctly and/or explain what you mean by 'stick with 6f8450a3f6e73832d52060a6ce5e44b08b587fee'.

I really would love to start that game and try it out, but that nasty error... :mad:


Re: Syscall ABI mismatch

Posted: Tue Jun 26, 2012 1:27 pm UTC
by danmal

You can set sv_pure on the command line by using the following command
./daemon.i386 +set sv_pure 0

Alternatively you can stick with this commit (f8450a3f6e73832d52060a6ce5e44b08b587fee). You should be able to revert to this commit by entering the following (you'll have to be in the Unvanquished dir)
git pull
git checkout v0.4.0-last-compat

If that doesn't work properly then download the following zip file.


Re: Syscall ABI mismatch

Posted: Tue Jun 26, 2012 6:43 pm UTC
by MoD

Thank you, 'git checkout 6f8450a3f6e73832d52060a6ce5e44b08b587fee' including a recompilation of the source code solved the issue.
I also tried './daemon.x86_64 +set sv_pure 0', but that gave me a segmentation fault.