Do you get the missing CXXABI_1.3.8 error when you run it on some hosted server or on the same machine you compiled the module on? Hosting services are known to keep running old versions, I've had issues with this a couple of years back when I compiled a module.
Try linking stdc++ statically. Search around how to do it, but probably
-static-libstdc++ is enough. Try linking everything statically with
-static as well. I don't know if there are any gotchas with that though that might screw you over later.
EDIT:
Actually there's a high probability that the main issue is that Valve ships their own libstdc++.so.6 with HL which only contains ABI up to CXXABI_1.3.3, which I think matches like GCC 4.7 or 4.8, because the last they updated it was in the 2013 Steam Pipe update. I believe that AMXX and modules don't even link to the standard library (or avoid it as much as possible) by disabling many C++ standard features, like exceptions, rtti etc. Look at AMBuildScript from amxmodx to see what exactly it does. I know you can add
-fno-exceptions and
-fno-rtti and that's what I've always used as well.
EDIT2:
Code:
strings -a libstdc++.so.6 | grep GCC:
reveals that it was compiled with GCC 4.6.1.
EDIT3:
Here's my usual setup that I've had no issues with:
https://github.com/rsKliPPy/customen...Script#L66-L89
__________________