Thanks for the report, I'll have a look at it, if there's anything I can see 
The make log mostly shows warnings that are known - va_list mangling change (damned gcc, 0.3 versions later and still printing this useless garbage)
About the warnings in Squirrel and CryptoPP, there's not much we can do about it - those are libraries that we just downloaded and integrated, we don't know (nor want to know) how they work. So until things are fixed in those libraries by their authors, nothing can be done.
Player respawns aren't handled correctly, that is known, I'll try to fix that.
What happens is that the client sends a packet that is used for login sequence, and MCServer, as a response, tries to authenticate the user.
By the way, seeing that "Assertion failed" message from the server means that you have compiled it in a debug configuration, therefore it's quite slow. If you compile with "make release=1", the server won't print out these messages, but it'll run much faster.
The make log mostly shows warnings that are known - va_list mangling change (damned gcc, 0.3 versions later and still printing this useless garbage)
About the warnings in Squirrel and CryptoPP, there's not much we can do about it - those are libraries that we just downloaded and integrated, we don't know (nor want to know) how they work. So until things are fixed in those libraries by their authors, nothing can be done.
Player respawns aren't handled correctly, that is known, I'll try to fix that.
What happens is that the client sends a packet that is used for login sequence, and MCServer, as a response, tries to authenticate the user.
By the way, seeing that "Assertion failed" message from the server means that you have compiled it in a debug configuration, therefore it's quite slow. If you compile with "make release=1", the server won't print out these messages, but it'll run much faster.