Yeah as to the above, he knows well the evil of all the MS operating systems...

He also will not allow a single windows based system anywhere on his entire network...

and he owns a rather large local broadband ISP...

he only allows BSD unix systems and that is it...

(but I think I may be weakening him on the linux idea) hehehe...

Yeah, I thought that filename variable containing garbage in the debug might be it... I will take a look, but I might just rather get it on Linux...

Anyway, thanks all for all your help...

I'm not a makefile guru, but it looks as if there are some .o files missing in your link statement (dbcore.o, for example). That would explain your undefined references. They were present during compile, but if your linker isn't adding all the .o files in during the link phase, it'll fail. The linker takes all its instructions from the makefile, so check there.

Regards,

krich

freebsd
 

Smells like you're using libstdc++ instead of liblstdc++ to link your final executable. This fun problem only manifests itself on 5.x, and is documented in the README.FreeBSD file in devel/linuxthread's work directory.

This document is pointed to in passing by the port after it finishes installing, but is easy to miss, and is not accessible unless you neglect to clean your port after installing.

See my thread at

http://www.everquestserver.com/forum...ic.php?t=12004

for patches against 0.5.3dr2 that allow for use of Perl and shared memory on FreeBSD 5.x with gcc 3.3.