• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Search results

  1. fluidsonic

    Linux Compiling tfs debian 7

    No, you're wrong - look closely. That's a whole different error. In Makefile.am look for "-Werror" (without quotes) and remove it. Then try again.
  2. fluidsonic

    Linux Compiling tfs debian 7

    In the TFS directory: apt-get remove lua5.2 lua50 liblua50 liblualib50 ./configure # add whatever options you need but make sure you run this again
  3. fluidsonic

    Linux Compiling tfs debian 7

    dpkg -l "*lua*" What does that output?
  4. fluidsonic

    Linux Compiling tfs debian 7

    http://otland.net/f16/compiling-ubuntu-64-os-194891/#post1881624 -> TFS needs LUA 5.1, not 5.2. apt-get remove liblua5.2-0 liblua5.2-0-dbg liblua5.2-dev And run ./configure again.
  5. fluidsonic

    Lua Linux Illegal instruction

    Did you compile TFS on the same server as you're running it? If not then you have to do so.
  6. fluidsonic

    Linux Bug which makes the serv closed !

    I don't think that this is the actual error. There is a bug in TFS which causes it to crash on shutdown only with this error. What is the log output before this crash happens?
  7. fluidsonic

    Compiling compiling in ubuntu 64 OS

    hm, difficult when not having the sources of TFS 0.4. Looks like LUA 5.2 doesn't even have lua_open anymore. Try uninstalling LUA 5.2 and run ./configure again. apt-get remove liblua5.2-0 liblua5.2-0-dbg liblua5.2-dev
  8. fluidsonic

    Lack of FOSS tools?

    You have enough control about it when offering stuff Open Source. Esp. sites like GitHub and BitBucket allow you to host your code and allow contributions by others which you have to approve first. No-one can mess with your stuff unless you allow it :) That shouldn't stop you! Software...
  9. fluidsonic

    Compiling compiling in ubuntu 64 OS

    Oh, looks like TFS 0.4 uses LUA 5.2. apt-get install liblua5.2
  10. fluidsonic

    Why is TFS 0.4 for premium only if?

    So you limit access to prevent other developers from eventually finishing it? :)
  11. fluidsonic

    Compiling compiling in ubuntu 64 OS

    Try apt-get install liblua5.1-0-dev
  12. fluidsonic

    Solved Linux Debian try download boost/libs

    apt-get update then try again
  13. fluidsonic

    Compilling Error [ I followed the TUT! ]

    Don't enable luaJIT when running ./configure - or install it. So run ./configure again without enabling luaJIT. I had lots of crashes when using luaJIT, so I'd just not use it.
  14. fluidsonic

    Compiling compiling in ubuntu 64 OS

    Is it possible that you use TFS 0.4? And that you compile it in a virtual machine? g++ optimizations seem to be problematic in some VMs. Look in all files for "-march=native" and "-mtune=native" and remove these options. Then try again.
  15. fluidsonic

    Compiling compiling in ubuntu 64 OS

    What do the following commands output: which g++ dpkg -l "*gcc*" dpkg -l "*g++*" uname -a cat /proc/cpuinfo gcc -march=native -Q --help=target gcc -march=native -E -v - </dev/null 2>&1 | grep cc1
  16. fluidsonic

    Compiling compiling in ubuntu 64 OS

    Are you sure that your CPUs there actually support 64 bit?
  17. fluidsonic

    Linux High CPU Usage

    Check that you have no decaying items in your otbm map - they cost somewhat much CPU. Many items in general cost much CPU. And having many NPCs too. Oh and globalevents which trigger too often. I'm currently adressing these issues with my own server...
  18. fluidsonic

    Solved Linux Map 100mb++

    You should use 64 bit in any case. But yes, the larger the map, the more memory you need. And the map needs a lot. In the end: just try it. It's not easy to predict memory usage.
  19. fluidsonic

    Compiling Illegal instruction

    This usually happens when you compile on a different machine than you run the resulting executable on. If you definitely did compile on the same machine, then the only other possible cause I can think of is that something corrupts your memory. But I think that's unlikely in your case.
  20. fluidsonic

    Linux High Memory Usage on x64

    This is perfectly normal for x64. Our server even uses 1.6 GiB. You shouldn't run a TFS on a server with less than 2-3 GiB anyway.
Back
Top