matpow2 / cuwo

Open server and utilities for Cube World
GNU General Public License v3.0
170 stars 49 forks source link

build.sh issue (UnicodeDecodeError) #154

Closed ghost closed 10 years ago

ghost commented 10 years ago

I'm having an error while compiling. I run build.sh and get the following: http://pastebin.com/Zu8U6thR Maybe it's a common issue, but I don't know why it doesn't work. Thank you.

ghost commented 10 years ago

And I do have both python-twisted and cython installed. Looks like there's a problem with encoding. Hmm.. It seems I should have read this: https://github.com/matpow2/cuwo/wiki/Linux I'll do all the steps and report tomorrow. I think my cython version is wrong.

ghost commented 10 years ago

Everything is OK. My versions: Cython version 0.19 Python 2.7.5+ twistd (the Twisted daemon) 13.0.0 the latest cuwo build cloned from github

What I'm doing wrong? I even run the script from root user, the same result.

MD5 sums: data1.db 5dd75c4fde12d1d1635e3791e26d22df data2.db 1efa0c3ce780250e195eab14e8797caa data3.db 5c27f768beb8a37dd5f3c42865778a47 data4.db b15f077653b02aac52e3ac365c7363e5 Server.exe a6fc5aa34068b5b80c53b2439c65be3b

ghost commented 10 years ago

Anyone? Do you have any Linux binaries?

ghost commented 10 years ago

FIX build.sh branch master: rename "python2.7" to python build.sh branch py3: rename "python2.7" to "python" Yeah. I did it! Leaving it opened until the bug is fixed.

grturner commented 10 years ago

This isn't a bug, just a difference in your build system versus that of the developer.

mid-kid commented 10 years ago

The "python" command should be a symlink to your distribution's preffered python version.

mid-kid@PocketRocket :: ~ $ ls -l $(which python)
lrwxrwxrwx 1 root root 7 27 abr 17:48 /usr/bin/python -> python3
mid-kid@PocketRocket :: ~ $ ls -l $(which python3)
lrwxrwxrwx 1 root root 9 27 abr 17:48 /usr/bin/python3 -> python3.4
mid-kid@PocketRocket :: ~ $ ls -l $(which python3.4)
-rwxr-xr-x 2 root root 10392 27 abr 17:48 /usr/bin/python3.4

If that isn't the case on your system, either your distribution tampered with the python package (python's default make install should create the correct symlinks), or you did that yourself. It's common practice for scripts which use a specific python (or any program which has multiple versions) version to point directly to said version. As a side note, it'd be really helpful if you said what distribution you use.

matpow2 commented 10 years ago

Yeah - python2.7 should definitely make it use the right version unless something is messed up on your distribution. Also, the py3 branch is not finished, so please do not use it yet.

As a side-question getsmp, does changing the commandline to /usr/bin/python2.7 or just python2.7 make it work? Using just python will make it use your preferred Python version, which won't necessarily be version 2.7.

ghost commented 10 years ago

I use Ubuntu 13.10. I'll try to change the command to /usr/bin... today.

ghost commented 10 years ago

It's misterious! /usr/bin/python is linked to python2.7, but now I cannot compile it again! What a luck suddenly happened to me yesterday... Guys, I'm lost in this puzzle :С

ghost commented 10 years ago

Hmm. It's my OS problem. I'm now compiling on Debian Wheezy, everything is OK without any changes in scripts.