Re: [hlcoders] Compiling under Linux for BSD
Any further thoughts on this? Would still like to see our stuff work under BSD. On Apr 27, 2005, at 9:11 PM, Jonathan Dance wrote: My mistake, it does actually call /usr/bin/gcc-3.4, not ld (I just assumed it was ld since it uses ld-like options). I don't believe we've modified the Makefile much at all from what was provided in linux_sdk, other than changing the necessary paths. Wish it was that easy... On Apr 27, 2005, at 4:43 PM, Alfred Reynolds wrote: You should be using gcc for the linking, not ld directly (gcc inserts some extra entries to the ld command line essentially). - Alfred -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Dance Sent: Wednesday, April 27, 2005 1:37 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] Compiling under Linux for BSD -- [ Picked text/plain from multipart/alternative ] OK, pardon my ignorance, but I'm not sure what this is supposed to show. I have a fairly long list of undefined symbols (88 to be exact) under linux, and it runs fine here. Should I do this under FreeBSD instead? Included in the list are the Q_ functions (like Q_strncpy, etc), DevWarning(), DevMsg(), as well as a bunch of other things like CVProfNode functions, some std functions and typedefs, and some globals like g_pMemAlloc, g_pVCR, and vtune. Would a full list be useful? It seems these are mostly things that would only be used in a Debug build. Are there not supposed to be any? If so, how do you fix them? I am compiling against glibc 2.3.2. I believe I'm doing so statically... the ld line looks like this: ld -shared -o ./server_i486.so all the mod object files -lm -ldl tier0_i486.so vstdlib_i486.so /usr/lib/gcc/i486-linux/3.4.4/libstdc+ +.a /usr/lib/gcc/i486-linux/3.4.4/libgcc.a Thoughts? Wish I knew more about how this all works. On Apr 26, 2005, at 4:01 PM, Alfred Reynolds wrote: Run: export LD_LIBRARY_PATH=.:bin:$LD_LIBRARY_PATH nm -g -C mod dir/bin/server_i486.so | grep U | grep -v GLIBC And see what undefined symbols remain. You may also be having a GLIBC versioning problem, you need at least 2.3.2 to run your mod, and you should compile your mod on a machine with 2.3.2 installed. - Alfred -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Compiling under Linux for BSD
-- [ Picked text/plain from multipart/alternative ] OK, pardon my ignorance, but I'm not sure what this is supposed to show. I have a fairly long list of undefined symbols (88 to be exact) under linux, and it runs fine here. Should I do this under FreeBSD instead? Included in the list are the Q_ functions (like Q_strncpy, etc), DevWarning(), DevMsg(), as well as a bunch of other things like CVProfNode functions, some std functions and typedefs, and some globals like g_pMemAlloc, g_pVCR, and vtune. Would a full list be useful? It seems these are mostly things that would only be used in a Debug build. Are there not supposed to be any? If so, how do you fix them? I am compiling against glibc 2.3.2. I believe I'm doing so statically... the ld line looks like this: ld -shared -o ./server_i486.so all the mod object files -lm -ldl tier0_i486.so vstdlib_i486.so /usr/lib/gcc/i486-linux/3.4.4/libstdc+ +.a /usr/lib/gcc/i486-linux/3.4.4/libgcc.a Thoughts? Wish I knew more about how this all works. On Apr 26, 2005, at 4:01 PM, Alfred Reynolds wrote: Run: export LD_LIBRARY_PATH=.:bin:$LD_LIBRARY_PATH nm -g -C mod dir/bin/server_i486.so | grep U | grep -v GLIBC And see what undefined symbols remain. You may also be having a GLIBC versioning problem, you need at least 2.3.2 to run your mod, and you should compile your mod on a machine with 2.3.2 installed. - Alfred -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
RE: [hlcoders] Compiling under Linux for BSD
You should be using gcc for the linking, not ld directly (gcc inserts some extra entries to the ld command line essentially). - Alfred -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Dance Sent: Wednesday, April 27, 2005 1:37 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] Compiling under Linux for BSD -- [ Picked text/plain from multipart/alternative ] OK, pardon my ignorance, but I'm not sure what this is supposed to show. I have a fairly long list of undefined symbols (88 to be exact) under linux, and it runs fine here. Should I do this under FreeBSD instead? Included in the list are the Q_ functions (like Q_strncpy, etc), DevWarning(), DevMsg(), as well as a bunch of other things like CVProfNode functions, some std functions and typedefs, and some globals like g_pMemAlloc, g_pVCR, and vtune. Would a full list be useful? It seems these are mostly things that would only be used in a Debug build. Are there not supposed to be any? If so, how do you fix them? I am compiling against glibc 2.3.2. I believe I'm doing so statically... the ld line looks like this: ld -shared -o ./server_i486.so all the mod object files -lm -ldl tier0_i486.so vstdlib_i486.so /usr/lib/gcc/i486-linux/3.4.4/libstdc+ +.a /usr/lib/gcc/i486-linux/3.4.4/libgcc.a Thoughts? Wish I knew more about how this all works. On Apr 26, 2005, at 4:01 PM, Alfred Reynolds wrote: Run: export LD_LIBRARY_PATH=.:bin:$LD_LIBRARY_PATH nm -g -C mod dir/bin/server_i486.so | grep U | grep -v GLIBC And see what undefined symbols remain. You may also be having a GLIBC versioning problem, you need at least 2.3.2 to run your mod, and you should compile your mod on a machine with 2.3.2 installed. - Alfred -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Compiling under Linux for BSD
My mistake, it does actually call /usr/bin/gcc-3.4, not ld (I just assumed it was ld since it uses ld-like options). I don't believe we've modified the Makefile much at all from what was provided in linux_sdk, other than changing the necessary paths. Wish it was that easy... On Apr 27, 2005, at 4:43 PM, Alfred Reynolds wrote: You should be using gcc for the linking, not ld directly (gcc inserts some extra entries to the ld command line essentially). - Alfred -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Dance Sent: Wednesday, April 27, 2005 1:37 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] Compiling under Linux for BSD -- [ Picked text/plain from multipart/alternative ] OK, pardon my ignorance, but I'm not sure what this is supposed to show. I have a fairly long list of undefined symbols (88 to be exact) under linux, and it runs fine here. Should I do this under FreeBSD instead? Included in the list are the Q_ functions (like Q_strncpy, etc), DevWarning(), DevMsg(), as well as a bunch of other things like CVProfNode functions, some std functions and typedefs, and some globals like g_pMemAlloc, g_pVCR, and vtune. Would a full list be useful? It seems these are mostly things that would only be used in a Debug build. Are there not supposed to be any? If so, how do you fix them? I am compiling against glibc 2.3.2. I believe I'm doing so statically... the ld line looks like this: ld -shared -o ./server_i486.so all the mod object files -lm -ldl tier0_i486.so vstdlib_i486.so /usr/lib/gcc/i486-linux/3.4.4/libstdc+ +.a /usr/lib/gcc/i486-linux/3.4.4/libgcc.a Thoughts? Wish I knew more about how this all works. On Apr 26, 2005, at 4:01 PM, Alfred Reynolds wrote: Run: export LD_LIBRARY_PATH=.:bin:$LD_LIBRARY_PATH nm -g -C mod dir/bin/server_i486.so | grep U | grep -v GLIBC And see what undefined symbols remain. You may also be having a GLIBC versioning problem, you need at least 2.3.2 to run your mod, and you should compile your mod on a machine with 2.3.2 installed. - Alfred -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
[hlcoders] Compiling under Linux for BSD
Hey everyone, I was wondering if anyone knew anything about compiling for BSD--when we distributed our server SO's for linux, some guys are running FreeBSD with linux emulation and it wouldn't work for them. They can run CS:S just fine though. Is there anything we can do to make the SOs compile under BSD? Thanks, --JD ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Compiling under Linux for BSD
On 4/26/05, Jonathan Dance [EMAIL PROTECTED] wrote: Hey everyone, I was wondering if anyone knew anything about compiling for BSD--when we distributed our server SO's for linux, some guys are running FreeBSD with linux emulation and it wouldn't work for them. They can run CS:S just fine though. Is there anything we can do to make the SOs compile under BSD? Are you using static or dynamic libc when linking? Try linking with the static libc (instead of using the .so) and see if that helps. Jeffrey botman Broome ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Compiling under Linux for BSD
I'm having the same problem. I'm compiling my mod in gentoo linux (Linux 2.6.11-gentoo-r5), and running srcds in freebsd (FreeBSD 5.3-RELEASE with linux_base-rh-9). In freebsd, srcds runs fine with hl2dm, but fails to load my mod with the following message: Auto detecting CPU Using AMD Optimised binary. Console initialized. Network: IP 127.0.0.1, mode MP, dedicated Yes, ports 27015 SV / 27005 CL Failed to load server_i486.so Failed to load server binary couldn't exec valve.rc In linux, I compared 'ldd server_i486.so' between hl2dm and my mod, and the output was identical. It would be wonderful if we could get native freebsd binaries for srcds, and compile the sdk natively.. but I'd love some help in getting it to run my linux binary. Not sure if the hlds_linux mailing list would be a better place for this, but while the thread is here.. =] Thanks! Casey epicar at dystopia-mod.com On 4/26/05, Jonathan Dance [EMAIL PROTECTED] wrote: Hey everyone, I was wondering if anyone knew anything about compiling for BSD--when we distributed our server SO's for linux, some guys are running FreeBSD with linux emulation and it wouldn't work for them. They can run CS:S just fine though. Is there anything we can do to make the SOs compile under BSD? Thanks, --JD ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
RE: [hlcoders] Compiling under Linux for BSD
Run: export LD_LIBRARY_PATH=.:bin:$LD_LIBRARY_PATH nm -g -C mod dir/bin/server_i486.so | grep U | grep -v GLIBC And see what undefined symbols remain. You may also be having a GLIBC versioning problem, you need at least 2.3.2 to run your mod, and you should compile your mod on a machine with 2.3.2 installed. - Alfred -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casey Bodley Sent: Tuesday, April 26, 2005 12:52 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] Compiling under Linux for BSD I'm having the same problem. I'm compiling my mod in gentoo linux (Linux 2.6.11-gentoo-r5), and running srcds in freebsd (FreeBSD 5.3-RELEASE with linux_base-rh-9). In freebsd, srcds runs fine with hl2dm, but fails to load my mod with the following message: Auto detecting CPU Using AMD Optimised binary. Console initialized. Network: IP 127.0.0.1, mode MP, dedicated Yes, ports 27015 SV / 27005 CL Failed to load server_i486.so Failed to load server binary couldn't exec valve.rc In linux, I compared 'ldd server_i486.so' between hl2dm and my mod, and the output was identical. It would be wonderful if we could get native freebsd binaries for srcds, and compile the sdk natively.. but I'd love some help in getting it to run my linux binary. Not sure if the hlds_linux mailing list would be a better place for this, but while the thread is here.. =] Thanks! Casey epicar at dystopia-mod.com On 4/26/05, Jonathan Dance [EMAIL PROTECTED] wrote: Hey everyone, I was wondering if anyone knew anything about compiling for BSD--when we distributed our server SO's for linux, some guys are running FreeBSD with linux emulation and it wouldn't work for them. They can run CS:S just fine though. Is there anything we can do to make the SOs compile under BSD? Thanks, --JD ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
