The official "ZDoom on Linux" thread.
Moderators: GZDoom Developers, Raze Developers
Forum rules
Please don't start threads here asking for help. This forum is not for requesting guides, only for posting them. If you need help, the Editing forum is for you.
Please don't start threads here asking for help. This forum is not for requesting guides, only for posting them. If you need help, the Editing forum is for you.
-
- Posts: 3288
- Joined: Sun Oct 03, 2004 8:57 am
- Preferred Pronouns: They/Them
- Location: South Africa
-
- Posts: 535
- Joined: Mon Aug 11, 2003 10:56 am
-
- Posts: 309
- Joined: Sat Nov 27, 2004 12:39 am
- Location: Teh Intarwebivurs
-
- Posts: 17
- Joined: Tue Aug 08, 2006 9:42 am
- Location: Padova, Italy
Very good Keep in mindit that isn't the final version, next week i'll submit an updated version on Gentoo BugzillaKrillancello wrote: scen: The ebuild works fine. I just had to make Portage ignore the ~x86 and then --digest it.
I thinks it would be quite simple, If i have some spare time i'll try to make them.Krillancello wrote: Now I wonder if we can setup some ebuilds for ACC, ZDBSP and ZETH.
-
- Posts: 4019
- Joined: Fri Aug 15, 2003 8:15 pm
- Location: ferret ~/C/ZDL $
-
- Posts: 309
- Joined: Sat Nov 27, 2004 12:39 am
- Location: Teh Intarwebivurs
-
- Posts: 17
- Joined: Tue Aug 08, 2006 9:42 am
- Location: Padova, Italy
Questions about compiling from source in Linux
Some question for ZDoom devs:
I'm making an ZDoom ebuild for Gentoo Linux, where almost every package is installed (and compiled, of course) from source.
I'm making an ZDoom ebuild for Gentoo Linux, where almost every package is installed (and compiled, of course) from source.
- is it safe to change CFLAGS in default Makefile.linux?
With default configuration they're set to:In this ebuild i want to substitute them with global CFLAGS set in Gentoo installation (in /etc/make.conf); for example, in my home linux system they ar -march i686 -O2 -pipe.eCode: Select all
without DEBUG: -pipe -Wall -Wno-unused -fno-strict-aliasing -O2 -fomit-frame-pointer -MMD -DHAVE_FILELENGTH -D__forceinline=inline -Izlib -IFLAC `sdl-config --cflags` -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNEED_STRUPR with DEBUG: -pipe -Wall -Wno-unused -fno-strict-aliasing -MMD -DHAVE_FILELENGTH -D__forceinline=inline -Izlib -IFLAC `sdl-config --cflags` -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNEED_STRUPR -D_DEBUG -g3
What are the "indispensable" CFLAGS (i think -Izlib -IFLAC `sdl-config --cflags` )? - Is it possible to make more "verbose" the compilation output (instead of elegant but somewhat useless "compiling abcde.foo [OK]" output style...)
-
- Posts: 4019
- Joined: Fri Aug 15, 2003 8:15 pm
- Location: ferret ~/C/ZDL $
-
- Posts: 3288
- Joined: Sun Oct 03, 2004 8:57 am
- Preferred Pronouns: They/Them
- Location: South Africa
I'd like a little help compiling ZDoom. I've done it before, so I'm sure it's not a 2.1.4 bug.
The output I'm getting is:
I'm trying to compile from "zdoom-2.1.4-src.7z" on Ubuntu 6.06 LTS 64bit.
I'm guessing the problem is I have not installed something which should be installed.
The output I'm getting is:
Code: Select all
make -C tools/updaterevision
make[1]: Entering directory `/home/player1/zdoomsrc/tools/updaterevision'
gcc -Os -Wall -fomit-frame-pointer -c -o updaterevision.o updaterevision.c
Linking updaterevision: [OK]
updaterevision.o: In function `main':updaterevision.c:(.text+0x5e): warning: the use of `tmpnam' is dangerous, better use `mkstemp'
make[1]: Leaving directory `/home/player1/zdoomsrc/tools/updaterevision'
sh: svnversion: command not found
mkdir releaseobj
Assembling a.nas: [OK]
Assembling misc.nas: [OK]
Assembling tmap2.nas: [OK]
Assembling tmap3.nas: [OK]
Assembling tmap.nas: [OK]
Compiling am_map.cpp: [ERROR]
g++ -fno-rtti -pipe -Wall -Wno-unused -fno-strict-aliasing -O2 -fomit-frame-pointer -MMD -DHAVE_FILELENGTH -D__forceinline=inline -Izlib -IFLAC -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNEED_STRUPR -Isrc/ -Isrc/g_doom/ -Isrc/g_heretic/ -Isrc/g_hexen/ -Isrc/g_raven/ -Isrc/g_shared/ -Isrc/g_strife/ -Isrc/oplsynth/ -Isrc/sound/ -Isrc/sdl/ -DUSEASM=1 -DNDEBUG -o releaseobj/am_map.o -c src/am_map.cpp
================================================================================src/am_map.cpp: In function ‘BOOL AM_clipMline(mline_t*, fline_t*)’:
src/am_map.cpp:1153: warning: ‘tmp$x’ may be used uninitialized in this function
src/am_map.cpp:1153: warning: ‘tmp$y’ may be used uninitialized in this function
{standard input}: Assembler messages:
{standard input}:141: Error: Incorrect register `%rcx' used with `l' suffix
{standard input}:176: Error: Incorrect register `%rdi' used with `l' suffix
{standard input}:484: Error: Incorrect register `%rcx' used with `l' suffix
{standard input}:497: Error: Incorrect register `%r8' used with `l' suffix
{standard input}:509: Error: Incorrect register `%r8' used with `l' suffix
{standard input}:520: Error: Incorrect register `%r8' used with `l' suffix
{standard input}:531: Error: Incorrect register `%rdi' used with `l' suffix
{standard input}:583: Error: Incorrect register `%rcx' used with `l' suffix
{standard input}:617: Error: Incorrect register `%rcx' used with `l' suffix
{standard input}:663: Error: Incorrect register `%rcx' used with `l' suffix
{standard input}:4958: Error: Incorrect register `%rcx' used with `l' suffix
{standard input}:4959: Error: Incorrect register `%r9' used with `l' suffix
{standard input}:4968: Error: Incorrect register `%rdx' used with `l' suffix
{standard input}:4969: Error: Incorrect register `%rcx' used with `l' suffix
make: *** [releaseobj/am_map.o] Error 1
I'm guessing the problem is I have not installed something which should be installed.
-
- Posts: 1031
- Joined: Wed Oct 15, 2003 12:19 am
- Location: Czech Republic
-
- Posts: 535
- Joined: Mon Aug 11, 2003 10:56 am
-
- Posts: 3288
- Joined: Sun Oct 03, 2004 8:57 am
- Preferred Pronouns: They/Them
- Location: South Africa
-
- Posts: 535
- Joined: Mon Aug 11, 2003 10:56 am
First of all, let me state that I don't use and haven't ever used Ubuntu or anything Debian-based and don't have a 64-bit processor. That said, here is what I think you have to do:
If they don't install, you have to enable installing from the "Universe" and possibly the "Multiverse" in Synaptic as describe here.
Then, once you compile zdoom using -m32, you can run it (and similarly for any other 32-bit Linux application) like so:
Lastly, this won't break you install. (Forcing the regular 32-bit libs to install over the 64-bit libs would, though.) The 32-bit libs will install alongside the 64-bit libs. They will only be used by gcc with the -m32 switch and by applications when they are run via linux32.
BTW, using 32-bit libs on a 64-bit architecture is much easier and better supported at the moment using an rpm-based distribution, especially SuSE.
Code: Select all
sudo aptget install ia32-libs ia32-libs-dev linux32
Then, once you compile zdoom using -m32, you can run it (and similarly for any other 32-bit Linux application) like so:
Code: Select all
linux32 zdoom
BTW, using 32-bit libs on a 64-bit architecture is much easier and better supported at the moment using an rpm-based distribution, especially SuSE.
-
- Posts: 3288
- Joined: Sun Oct 03, 2004 8:57 am
- Preferred Pronouns: They/Them
- Location: South Africa
-
- Lead GZDoom+Raze Developer
- Posts: 49183
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany