Threaded Mode | Linear Mode

***Coruja*** · 11-15-2016 02:05 PM

Anyone here is using 56d nightlies on linux?

I'm trying here on CentOS 7.2 (64bit) but it seems quite broken. 56c also have some problems. It's my first time using linux, and unfortunately I don't have enough knowledge to fix this thing alone

56d builds on windows are running perfectly fine and stable, but on linux I can't even launch sphere without get tons os console errors (eg: weird linux memory errors, scripts files that exists but it's not being read at server startup, etc)

I'm planning to make linux builds stable as the windows builds, so if you're an linux user, I invite you to join our source code project on github, to send pull requests, report bugs, update linux guides, etc. Every help will be appreciated, and together we can make linux builds great again Smile

Criminal · 11-15-2016 07:01 PM

Check capital letters in spheretables when loading scripts > scripts/Item.scp if in the folder is item.scp it will not be loaded

I remember run 56c in centos 7 or 6 i dont rmember, and was working good

Kanibal · 11-15-2016 08:04 PM

(11-15-2016 07:01 PM)Criminal Wrote: Check capital letters in spheretables when loading scripts > scripts/Item.scp if in the folder is item.scp it will not be loaded

Oh yes, that was a little problem for me to Tongue

(11-15-2016 07:01 PM)Criminal Wrote: I remember run 56c in centos 7 or 6 i dont rmember, and was working good

I run 56b in Ubuntu Server 12.04 and that was fine Veryhappy

***Ben*** · 11-15-2016 10:13 PM

imho the biggest problem with making the linux build stable, is that there are so many distros with different libs, it's just not possible.
The best possible solution is to compile it directly on the distro you are using

Kanibal · 11-15-2016 11:00 PM

(11-15-2016 10:13 PM)Ben Wrote: ...that there are so many distros with different libs...

SphereBuntu Devil

***Coruja*** · 11-16-2016 02:35 AM

I'm trying to compile directly on my CentOS server but always get this error when I type "make NIGHTLY=1 -f makefile" on terminal

Code:

Current build revision: 251 (GIT hash: 72ff099)

Compiler Flags: g++ -c -Wall -Wno-unknown-pragmas -Wno-invalid-offsetof -Wno-unused-but-set-variable -Wno-switch -pipe -fexceptions -fnon-call-exceptions -s -00 -fno-expensive-optimizations -fno-omit-frame-pointer -ffast-math -fpermissive -I./src/common -I/usr/include/mysql -D_GRAY_SVR -D_CONSOLE -D_REENTRANT -D_LINUX -D_NIGHTLYBUILD -D_MTNETWORK

  ...

  Compiling src/common/sqlite/sqlite3.c

/bin/ld: cannot find -lmysqlclient

collect2: error: ld returned 1 exit status

make: *** [spheresvr] Error 1

PS: these 3 packages are already installed:
-yum install mysql
-yum install mysql-libs
-yum install mysql-devel

EDIT: Compiler is working fine now, but using the compilated spheresvr file I'm having tons of errors on console. There's so many errors that sphere always return "Server unstable - closing" before finish loading proccess.

these problems occur using both spheresvr file compiled on the same PC and spheresvr file generated from automated GIT / Travis-CI server (Ubuntu/Linaro 4.6.3-1ubuntu5)

EDIT²: I finally found the problem, sphere is 32bit and must run in 32bit even on 64bit OS, but both spheresvr files that I had tried was compiled in 64bit, making it very unstable.
I just changed the compiler to build using 32bit and now everything is running fine (at least for now) Big Grin

So the problem with sphere on linux is not a fault on source code, but just a lack of updated guides/instructions telling what the user must do to make everything work properly

Threaded Mode \| Linear Mode Problems on 56d Linux builds
Author	Message