glib trouble

[Hugo (6s-gaming.com)]

i,

I have this problem on a 4.8-RELEASE-p13 server, whenever compiling
something related with glib:

(...)
/usr/lib/libstdc++.so: undefined reference to `__strtol_internal at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `malloc at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `strdup at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `fclose at GLIBC_2.1'
/usr/lib/libstdc++.so: undefined reference to `stdout at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `fileno at GLIBC_2.0'
/usr/lib/libgcc_s.so.1: undefined reference to `__bzero at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `strcoll at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `fprintf at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `strxfrm at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `strlen at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `__errno_location at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `stderr at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `strcat at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `fwrite at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `fdopen at GLIBC_2.1'
/usr/lib/libstdc++.so: undefined reference to `memmove at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `ungetc at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `__ctype_b at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `fopen at GLIBC_2.1'
/usr/lib/libstdc++.so: undefined reference to `__strtod_internal at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `printf at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `abort at GLIBC_2.0'
/usr/lib/libstdc++.so: undefined reference to `__strtof_internal at GLIBC_2.0'


I initially added libstdc++ to the system via wget (googled it), because
version 1.2 of Call of Duty server required it. I have another server on
4,8-STABLE, and I downloaded its libstdc++ (no problems compiling there)
to this system, but the problem remains. Anyone ever ran into this
problem?

Kind regards,

Hugo
-- 


-- 
http://www.6s-gaming.com - your online store!