progress

[tschumann]

Alright, so looks like a discrepancy between the version of libstdc++ I compiled with and the versions on your systems: https://stackoverflow.com/a/35394410/5158636, https://github.com/FoldingAtHome/fah-issues/issues/1147

Can you both ldd sandbot.so then ls -ali the path to libstdc++.so.6 - for me the symlink points to libstdc++.so.6.0.22 which I guess is pretty recent
@RoboCop if you're on Ubuntu 14 you might need to compile yourself or possibly update libstdc++ to a newer version if possible.
@Nubzior you seem to be on a pretty recent version of Debian so might only be off by a minor version. Do the above anyway and we'll see what's what.

[RoboCop]

Originally Posted by tschumann

Alright, so looks like a discrepancy between the version of libstdc++ I compiled with and the versions on your systems: https://stackoverflow.com/a/35394410/5158636, https://github.com/FoldingAtHome/fah-issues/issues/1147

Can you both ldd sandbot.so then ls -ali the path to libstdc++.so.6 - for me the symlink points to libstdc++.so.6.0.22 which I guess is pretty recent
@RoboCop if you're on Ubuntu 14 you might need to compile yourself or possibly update libstdc++ to a newer version if possible.
@Nubzior you seem to be on a pretty recent version of Debian so might only be off by a minor version. Do the above anyway and we'll see what's what.

Did you try using clang++ compiler instead of g++? Also I use my Linux Mint Laptop for recompiling some broken Metamod addons. I'll give the recompiling for SB a go

[tschumann]

I don't think that using clang would fix this - I think it's the version of libstdc++ I have installed. What's the name of the file that gets symlinked on your KUbuntu 14?

[RoboCop]

Well I'm quite sure how to find my symlink for libstdc++, I did try this but don't seem to work and that file does exist in my Ubuntu 14.04:-

$ ls -l usr/lib32/libstdc++.so.6
ls cannot access	usr/lib32/libstdc++.so.6: No such file or directory

Using [readlink -f usr/lib32/libstdc++.so.6] didn't reply or print anything with that command.

Also I cannot seem to recompile your latest beta build on both my Ubuntu 14.04 and my Linux Mint 18.2 Cinnamon Laptop:-

waypoint.cpp: In function 'bool WaypointLoad(edict_t*)':
waypoint.cpp:1573:71: error: 'static_assert' was not declared in this scope
           static_assert(sizeof(WAYPOINT) == 24, "WAYPOINT should be 24 bytes");

[tschumann]

Can you ldd sandbot.so and then ls -ali the path it gives to libstdc++.so.6?

Looks like static_assert is a newer feature of C++ (see https://stackoverflow.com/questions/...ic-assert-in-c) - you should just be able to comment out those lines and compile.

[RoboCop]

Well you be pleased to know from when I commented out those 'static_assert' lines and recompiled sandbot in my Linux Mint it appears to be working now, BUT only in standalone "liblist.gam" mode. I did try sandbot loaded only from Metamod but they don't seem to be selecting which team they can randomly pick.

And here is the ldd and ls -ali results of this recompiled sandbot.so:-

https://www.dropbox.com/s/ec4cnf1gkv1ci32/ldd.jpg?dl=0

[tschumann]

Great, so it's not a bug with Sandbot as such!

With MetaMod you were trying Opposing Force CTF? What was the problem exactly? I know that the bots currently don't join teams to create even teams.

What version of gcc do you have installed locally? I have v6.3.0 but libstdc++.so.6.0.24 suggests you have gcc v7.x.x installed.

[RoboCop]

Originally Posted by tschumann

Great, so it's not a bug with Sandbot as such!

With MetaMod you were trying Opposing Force CTF? What was the problem exactly? I know that the bots currently don't join teams to create even teams.

What version of gcc do you have installed locally? I have v6.3.0 but libstdc++.so.6.0.24 suggests you have gcc v7.x.x installed.

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.5-2ubuntu1~14.04.1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.5 (Ubuntu 4.8.5-2ubuntu1~14.04.1)

And the MetaMod is MM v1.21-p37.

[tschumann]

Hm, so it's an older version of gcc but it looks like you have a pretty new version of libstdc++ installed - mine in 6.3.0-12 but yours is 6.3.0-18. Are you using a non-Ubuntu repo/mirror?
Reading https://gcc.gnu.org/onlinedocs/libst...anual/abi.html it looks like using new libraries while linking with old libraries should work, but doesn't as we can see.

[RoboCop]

I've installed it from Ubuntu Software Centre. I didn't use PPA or using any repos from launchpad for libstdc++ nor GCC for Lubuntu 14.04.