Comments on: Running Doom under Linux

By: Greg

Greg — Tue, 24 Jan 2012 02:09:36 +0000

I got the original doom to work on Arch Linux with X server 1.11.3 and the vesa driver. I don’t know if this is specific to my system but the colors were displaying incorrectly. Apparently the color map wasn’t taking affect because it wasn’t installed. The color map can be installed immediately after creation (i_video.c:794):

XInstallColormap(X_display, X_cmap);

This seems to be a necessary step and I don’t know why it wasn’t done originally. Maybe it’s a requirement of more recent X servers.

By: Steve

Steve — Sat, 31 Dec 2011 23:51:00 +0000

Some more fixes for you:

dstrings.h lines 46 & 55 require commas at the end. This stops linuxdoom crapping out at the quit message. Also, add a space at the end of the string in line 50: …at the dos prompt! ” – This makes sure the whole string is displayed.
doomdef.h line 34 should be 109 and not 110. This will make demos work.

Linuxdoom compiles fine under Debian Squeeze BTW.

By: Steve

Steve — Mon, 26 Dec 2011 18:40:39 +0000

Thanks. That’s fixed it.

I’m also working on making the code 64 bit compatible. That’s a lot of work, but will be worth it. It’s mainly fixing the pointers for wad loading, that is, according to Fraggle.

Wish me luck!

By: narc

narc — Tue, 13 Dec 2011 01:39:58 +0000

Ugh! Nearly 1½ year later and compiling the basic code under Ubuntu 64-bits is a hassle, to which I now have no solution. (I used a 32-bits system back then). /me thinks the gcc compiler was updated to support stronger typing: I have a bunch of illegal casting of char * to int * that probably an old, more forgetful compiler would accept.

Fortunately, I could compile the sound server. Your problem is similar to what I read in a different forum and which I was able to reproduce (with a different signal though). I simply forgot to indicate a change in linux.c:56, to also eliminate the extern int errno in the same fashion as above and include somewhere at the top.

Hope this works. And if you have some additional tips about my compilation problem, feel free to contribute.

By: Steve

Steve — Sun, 11 Dec 2011 19:37:02 +0000

I cannot get the soundserver to compile. Trouble with linking. No errors or warnings, just:
collect2: ld terminated with signal 11

By: HJunk

HJunk — Mon, 24 Jan 2011 11:47:17 +0000

I solved at last. Shareware .was is not accepted. To avoid problems like “W_InitFiles not found” you can either create a bash file or run doom with the command:

./linuxxdoom -game save -file /home/USER/Desktop/linuxdoom-1.10/linux/doom.wad -userid /home/USER/Desktop/linuxdoom-1.10/linux/save

where: .wad has to be the original one.
USER is the user folder
save is a folder that has to be created to save game

By: HJunk

HJunk — Mon, 24 Jan 2011 08:38:34 +0000

Ok. I get it and Ive compiled the linuxdoom1.10 version instead of the SDL one. Neither I can compile sndserv ( got segmentation fault ) nor I can run the linuxxdoom as it doesnt find the .wad file (it says W_InitFiles no files found ). What can I do?

Thanks

By: narc

narc — Mon, 24 Jan 2011 05:57:49 +0000

@HJunk Please read the comment above yours (!?) My tutorial is about the original Doom source code while baxzius had problem with LsdlDoom (not to be confused with SDLDoom, see above), a heavily modified port and extension to which I don't provide any solution. I abondonned the idea to run that program altogether. Sorry if there was any confusion.

By: HJunk

HJunk — Sun, 23 Jan 2011 20:26:15 +0000

How the hell is possible to solve the problem that baxzius also had? I mean I hate tutorial where everything seems so clear..

By: narc

narc — Wed, 15 Sep 2010 00:40:36 +0000

@baxzius
I’m not a real fan of this version. It took me a while to compile it (link errors galore between C and ASM object files) and found it incredibly difficult to follow with unmistakable errors that old compilers might let go but unforgivable in terms of actual C syntax (extern on static variables ???). The changes in the info.c file are unwarranted if you only wish to play with the shareware version (Why does it tell me that CRBRICK is missing? Are there other PWADs ?).

As for your actual problem, I did not experience it although I couldn’t run the game myself either. ‘IWAD’ are the first 4 characters of an official .wad file (the homebrew versions are PWADs). Open up that file up and check the header. Your answer lies in file d_wad.c, lines 635-85. Use a debugger and check the IWAD’s compatibility with the actual linuxdoom you compiled earlier.

Good luck.