SUSE Linux/Tumbleweed build doese not work #1339

LowLevelMahn · 2024-10-11T10:40:03Z

latest Tumbleweed with all build essentials + gcc 14.2 + dosbox installed

git clone https://github.com/open-watcom/open-watcom-v2.git

(didn't copied the setvars.sh)

diff --git a/setvars.sh b/setvars.sh
index d011833882..cfb5ad7024 100755
--- a/setvars.sh
+++ b/setvars.sh
@@ -34,12 +34,12 @@ export OWDOCBUILD=0
 # It doesn't requires appropriate DOSBOX emulator
 # and suppress documentation build

-# export OWNOWGML=1
+export OWNOWGML=1

 # Set OWGUINOBUILD variable to 1 to suppress tools GUI version build
 # If it is used then only tools character mode version is build

-# export OWGUINOBUILD=1
+export OWGUINOBUILD=1

 # Set OWNOBUILD variable to list of OW projects to suppress their build
 # Example export OWNOBUILD=ide browser dlgprs
@@ -72,7 +72,7 @@ export OWDISTRBUILD=0
 # if DOSBOX emulator is used then OWDOSBOX variable must be set
 # Uncoment and set OWDOSBOX variable bellow to point to DOSBOX emulator executable

-# export OWDOSBOX=dosbox
+export OWDOSBOX=dosbox

./setvars.sh
./build.sh

returns

Open Watcom build environment (GCC version=14)
wmake bootstrap build error

The text was updated successfully, but these errors were encountered:

jmalak · 2024-10-11T15:31:45Z

please check build/binbuild/bootx.log for messages.
Probably gcc version 14 generate some new messages and need to fix them.

LowLevelMahn · 2024-10-11T15:34:44Z

here the content of the bootx.log

linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2/build/binbuild> cat bootx.log
rm -f *.o *.gh *.exe
c99 -g -O2 -I. -I../h -I../../watcom/h -I../../lib_misc/h -D__LINUX__ -D__UNIX__ -DBOOTSTRAP -DINCL_MSGTEXT -D_POSIX_C_SOURCE=200112L -D_BLDVER=1300 -D_CYEAR=xxxx -c ../../builder/c/wsplice.c
c99: invalid option -- '2'
usage: c99 [-c] [-D name[=value]] [...] [-E] [-g] [-I directory ...]
       [-L directory ...] [-o outfile] [-O] [-s] [-U name ...] operand ...

       where operand is one or more of file.c, file.o, file.a
       or -llibrary
make: *** [../posmake:69: wsplice.o] Error 1

according to the manual c99 is a shell wrapper script to cc - which is also version 14.2

jmalak · 2024-10-11T15:51:48Z

It looks like change or bug in c99 for your installation.
The problem is with -O2 option of full command

c99 -g -O2 -I. -I../h -I../../watcom/h -I../../lib_misc/h -D__LINUX__ -D__UNIX__ -DBOOTSTRAP -DINCL_MSGTEXT -D_POSIX_C_SOURCE=200112L -D_BLDVER=1300 -D_CYEAR=xxxx -c ../../builder/c/wsplice.c

LowLevelMahn · 2024-10-11T15:57:53Z

It looks like change or bug in c99 for your installation.

i have ask on the gcc mailing list

jmalak · 2024-10-11T16:11:33Z

I tried it with gcc 12 and no problem with -O2 option.
I don't know what shell you use, OW build system suppose POSIX compatible Korn/Bash shell.

LowLevelMahn · 2024-10-11T16:13:31Z

I don't know what shell you use, OW build system suppose POSIX compatible Korn/Bash shell.

echo "$SHELL"
/bin/bash

bash --version
GNU bash, version 5.2.37(1)-release (x86_64-suse-linux)

LowLevelMahn · 2024-10-11T16:47:37Z

on Ubuntu
the /usr/bin/c99 is a link to an script that just calls gcc

on Tumbleweed its some (c compiler related) binary with no link to gcc - even the manual looks different to Ubuntu/Debian

jmalak · 2024-10-11T17:45:24Z

It doesn't matter, c99 command line is defined by POSIX standard.

-O  optlevel
Specify the level of code optimization. If the optlevel option-argument is the digit '0', all special code 
optimizations shall be disabled. If it is the digit '1', the nature of the optimization is unspecified. 
If the -O option is omitted, the nature of the system's default optimization is unspecified. It is unspecified
whether code generated in the presence of the -O 0 option is the same as that generated when -O is omitted.
Other optlevel values may be supported.

that optlevel value can be toolchain specific.

LowLevelMahn · 2024-10-12T05:21:57Z

its a bug in Tumbleweed: https://bugzilla.opensuse.org/show_bug.cgi?id=1156949

try building with my Fedora 40 (gcc 14.2.1) seems to work - so i need to get some pressure on the Tumbleweed guys or patch your make files to use gcc -std=c99 instead of c99 (or something fitting)

jmalak · 2024-10-12T06:37:00Z

It is not possible because we relate on POSIX c99 not on gcc in pre-boot phase for *NIX systems (by example it uses c99 on OSX etc.
This pre-boot phase must be portable and cannot depend on any specific compiler therefore we use POSIX c99.
I can do exception for gcc but I am not sure how gcc command line is different from c99 syntax.

LowLevelMahn · 2024-10-12T06:43:06Z

It is not possible because we relate on POSIX c99 not on gcc in pre-boot

on Fedora 40: c99 is some small binary - seems to exec gcc
on Ubuntu 24.04.1 LTS: c99 is just a shell script that calls gcc

/usr/bin/c99 -> /etc/alternatives/c99

cat /etc/alternatives/c99
#! /bin/sh

# Call the appropriate C compiler with options to accept ANSI/ISO C
# The following options are the same (as of gcc-3.3):
# 	-std=c99
# 	-std=c9x
# 	-std=iso9899:1999
# 	-std=iso9899:199x

extra_flag=-std=c99

for i; do
    case "$i" in
	-std=c9[9x]|-std=iso9899:199[9x])
	    extra_flag=
	    ;;
	-std=*|-ansi)
	    echo >&2 "`basename $0` called with non ISO C99 option $i"
	    exit 1
	    ;;
    esac
done

exec gcc $extra_flag ${1+"$@"}

LowLevelMahn · 2024-10-12T06:47:56Z

the build fails on Fedora 40 gcc 14.2.1 and clang 18.1.8 this way (both builds giving same error messages)

...
./mkcode.exe copystub.gh
bld_as decstub.obj
bld_link decstub.tmp
../../asm/decstub.asm(268): Note! N293: Extending jump
../../asm/decstub.asm(285): Note! N293: Extending jump
../../asm/decstub.asm(268): Note! N293: Extending jump
../../asm/decstub.asm(285): Note! N293: Extending jump
./mkcode.exe decstub.gh
cc cwc.obj
cl cwc.exe
/usr/bin/ld: cannot find -lc: No such file or directory
collect2: error: ld returned 1 exit status
Error(E42): Last command making (cwc.exe) returned a bad status
Error(E02): Make execution terminated
<pmake -d build          -h> => non-zero return: 512
Build failed

jmalak · 2024-10-12T06:54:03Z

It will need to modify bld/wmake/posmake (POSIX make file) to use gcc command instead of c99 if gcc toolchain is used.
I will try to change and test.
The -lc option should be option to include standard C library. try to go to bld/causeway/cwc and run builder clean and next builder build OWVERBOSE=1 to get full command line.

LowLevelMahn · 2024-10-12T07:01:46Z

test@fedora:~/temp/open-watcom-v2_dev/open-watcom-v2_gcc$ cd bld/causeway
test@fedora:~/temp/open-watcom-v2_dev/open-watcom-v2_gcc/bld/causeway$ builder clean
bash: builder: command not found...
test@fedora:~/temp/open-watcom-v2_dev/open-watcom-v2_gcc/bld/causeway$ ./builder clean
bash: ./builder: No such file or directory

jmalak · 2024-10-12T07:31:50Z

It suppose you have setup OW build environment and have run OW build up to break.

Anyway I did workaround fix for you, modify your build.sh to be as following code to fix issue with c99 and gcc 14.

if [ "$OWTOOLS" = "WATCOM" ]; then
    output_redirect wmake -m -f ../wmake clean
    output_redirect wmake -m -f ../wmake
else
    if [ "$OWTOOLS" = "GCC" ]; then
        if [ "$OWTOOLSVER" = "14" ]; then
            # workaround for gcc 14 on SUSE
            TCC="CC=gcc"
        fi 
    fi
    case `uname` in
        FreeBSD)
            output_redirect make -f ../posmake clean
            output_redirect make -f ../posmake TARGETDEF=-D__BSD__ $TCC
            ;;
        Darwin)
            output_redirect make -f ../posmake clean
            output_redirect make -f ../posmake TARGETDEF=-D__OSX__ $TCC
            ;;
        Haiku)
            output_redirect make -f ../posmake clean
            output_redirect make -f ../posmake TARGETDEF=-D__HAIKU__ $TCC
            ;;
#        Linux)
        *)
            output_redirect make -f ../posmake clean
            output_redirect make -f ../posmake TARGETDEF=-D__LINUX__ $TCC
            ;;
    esac
fi

LowLevelMahn · 2024-10-12T07:43:42Z

It suppose you have setup OW build environment and have run OW build up to break.

i try that

Anyway I did workaround fix for you, modify your build.sh to be as following code to fix issue with c99 and gcc 14.

compilations starts and seems to work

LowLevelMahn · 2024-10-12T07:44:18Z

i got a compilation error on Ubuntu 24.10 (also with gcc 14.2.x) --> #1340

cc guixloop.obj
../c/guixloop.c: In function ‘GUICreatePopup’:
../c/guixloop.c:227:38: error: passing argument 2 of ‘GUICreateMenuPopup’ from incompatible pointer type [-Wincompatible-pointer-types]
  227 |     ui_ev = GUICreateMenuPopup( wnd, &scr_location, wnd->menu, GUI_TRACK_LEFT, NULL );
      |                                      ^~~~~~~~~~~~~
      |                                      |
      |                                      guix_coord *
In file included from ../c/guixloop.c:40:
../../../../bld/gui/ui/h/guifloat.h:34:66: note: expected ‘guix_point *’ but argument is of type ‘guix_coord *’
   34 | extern ui_event GUICreateMenuPopup( gui_window *wnd, guix_point *scr_location, UIMENUITEM *menuitems,
      |                                                      ~~~~~~~~~~~~^~~~~~~~~~~~
Error(E42): Last command making (guixloop.obj) returned a bad status
Error(E02): Make execution terminated
<pmake -d build          -h> => non-zero return: 512
Build failed

LowLevelMahn · 2024-10-12T07:45:11Z

don't be confused: im currently building openwatcom on recent Tumbleweed/Ubuntu 24.10 and Fedora 40 in parallel :)

LowLevelMahn · 2024-10-12T07:56:11Z

It suppose you have setup OW build environment and have run OW build up to break.

i try that

i did run my ./setvar.sh and ./build.sh up to break but the builder command don't get found afterwards?

jmalak · 2024-10-12T08:03:33Z

Run sh build.sh preboot and check in build/binbuild if there is wmake and builder compiled executable.
check build/binbuild/bootx.log if builder is created.

jmalak · 2024-10-12T08:05:37Z

May be a problem that you use template script setvars.sh instead of your own configured script created from this template.

LowLevelMahn · 2024-10-12T08:07:16Z

Run sh build.sh preboot and check in build/binbuild if there is wmake and builder compiled executable.

linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2> sh build.sh preboot
Open Watcom build environment (GCC version=14)
linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2> ls build/binbuild/
aliasgen  bmp2eps    bspecs.owc  bwasm    bwcc386  bwcl386  bwhc    bwpp386  chk_exec  cvtutf8   genverrc   mkinf     objxdef   parsedyn   uzip    wsplice
bcwc      boot.lo1   builder     bwasmps  bwccaxp  bwclaxp  bwipfc  bwppaxp  chktest   dlgprs    hcdos      msgencod  objxref   re2c       vicomp  yacc
bdmpobj   boot.log   build.lo1   bwasppc  bwccmps  bwclmps  bwlib   bwrc     comstrip  errdoc    kanji.uni  objchg    optencod  ssl        wcpp
bedbind   bootx.log  build.log   bwbind   bwccppc  bwclppc  bwlink  bwstrip  cpyright  errsrc    langdat    objfind   parsectl  sweep      whpcvt
bide2mak  bowcc      bwasaxp     bwcc     bwcl     bwdis    bwpp    catfile  crlf      findhash  mkexezip   objlist   parsedlg  to932.uni  wmake

both available

jmalak · 2024-10-12T08:09:12Z

for sure run sh clean.sh before sh build.sh ... to cleanup all residual build objects.

LowLevelMahn · 2024-10-12T08:09:30Z

May be a problem that you use template script setvars.sh instead of your own configured script.

i will fresh re-clone, copy the setvars.sh into my own, apply your c99 patch and retry

LowLevelMahn · 2024-10-12T08:09:52Z

for sure run sh clean.sh before sh build.sh ... to cleanup all residual build objects.

did that - work with just ./clean.sh

LowLevelMahn · 2024-10-12T08:23:57Z

May be a problem that you use template script setvars.sh instead of your own configured script created from this template.

i changed that for the freshly started Tumbleweed and Fedora build - Ubuntu seems to get further without doing that... but i'll give it a try

LowLevelMahn · 2024-10-12T08:45:56Z

the freshly started Tumbleweed build fails as before - fresh git clone/build.sh c99 patch at the same location

...
bld_as decstub.obj
bld_link decstub.tmp
../../asm/decstub.asm(268): Note! N293: Extending jump
../../asm/decstub.asm(285): Note! N293: Extending jump
../../asm/decstub.asm(268): Note! N293: Extending jump
../../asm/decstub.asm(285): Note! N293: Extending jump
./mkcode.exe decstub.gh
cc cwc.obj
cl cwc.exe
/usr/lib64/gcc/x86_64-suse-linux/14/../../../../x86_64-suse-linux/bin/ld: cannot find -lc: No such file or directory
collect2: error: ld returned 1 exit status
Error(E42): Last command making (cwc.exe) returned a bad status
Error(E02): Make execution terminated
<pmake -d build          -h> => non-zero return: 512
Build failed
linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2>

im sitting right there

linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2> ls build/binbuild/ | grep 'builder\|wmake'
builder
wmake

linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2> cd bld/causeway/
linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2/bld/causeway> builder clean
-bash: builder: command not found
linux@DESKTOP-G8ILNGQ:~/temp/open-watcom-v2_dev/open-watcom-v2/bld/causeway>

but builder seems not findable due to my path environment - how should that work?

echo "$PATH"
/home/test/.local/bin:/home/test/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin

Tumbleweed and Fedora got same error and behave the same with builder clean - Ubuntu runs and runs

it fails also the same on Ubuntu when i (sensless) try to do the same on Ubuntu when the compilation error (#1341) happens

jmalak · 2024-10-12T08:56:29Z

it looks like you have incorrectly setup OW build environment.
You need to run your setup script before you work in build environment.
It setup PATH to contains OW build binaries, you don't have it setup that you do something wrong (not run setup script).
Setup script must be run by . <setup script> to hold changed environment.

LowLevelMahn · 2024-10-12T09:02:27Z

it looks like you have incorrectly setup OW build environment.
You need to run your setup script before you work in build environment.

where is this setup-script? im calling my copy of setvars.sh ./my_setvars.sh (with correctly set OWROOT,dosbox) and then ./build.sh
is there some other script? can't find that clearly in the docs

jmalak · 2024-10-12T09:06:29Z

no, only this one but you must run it by . ./my_setvars.sh to hold changes but you run it as ./my_setvars.sh what is wrong.

jmalak · 2024-10-13T09:48:39Z

If you removed OWGUINOBUILD=1 then it will be build all GUI tools that this issue cannot happen.
Now build with OWGUINOBUILD=1 should works correctly.

LowLevelMahn · 2024-10-13T10:23:16Z

still problems - because Tumblewee (also Fedora) uses dosbox-staging as default - dosbox aborts somewhere in between - need first ask the dosbox-staging guys to fix that - will test it later then again

jmalak · 2024-10-13T10:36:07Z

OK. If it needs some special setup we can do it similar for OSX which need the changes.

LowLevelMahn · 2024-10-13T10:37:43Z

Issue on dosbox-staging: dosbox-staging/dosbox-staging#3984

jmalak · 2024-10-13T10:40:06Z

Anyway you can try it with OWNOWGML=1 and all remaining setup as default.
It should suppress build only if it needs WGML tool (documentation and a few tools) that it should build most of OW build including GUI tools.

LowLevelMahn · 2024-10-13T10:44:40Z

Anyway you can try it with OWNOWGML=1 and all remaining setup as default. It should suppress build only if it needs WGML tool (documentation and a few tools) that it should build most of OW build including GUI tools.

i'll try that and give feedback

so open bugs:

Tumbleweed: the c99 bug and the problem with the problem default dosbox-staging
Fedora: only the problem default dosbox-staging

nothing you can fix

jmalak · 2024-10-13T10:47:50Z

We have temporary workaround for both.
c99 bug - change build script
DOSBOX - suppress use of wgml at all

LowLevelMahn · 2024-10-13T10:48:11Z

regarding the dosbox-staging fail

is it possible to just build that part so the dosbox-staging devs can only build that for testing?
there are two screenshots showing the problem part while building: dosbox-staging/dosbox-staging#3984

both at bld/browser/nt386

i tried

. ./my_set_vars.sh
./build.sh preboot
cd bld/browser/
builder build

but that fails with

**** BUILD rule
=== 12:59:27 /home/test/temp/open-watcom-v2_dev/open-watcom-v2/bld/browser ====
= 12:59:27 /home/test/temp/open-watcom-v2_dev/open-watcom-v2/bld/browser/gen ==
dlgprs ../res/dlg/dgenums.dlg ../bnd/dgenums.bnd dgenums.gh dgenums.gpp
sh: line 1: dlgprs: command not found
Error(E14): Cannot execute (dlgprs): command not found
Error(E42): Last command making (dgenums.gpp) returned a bad status
Error(E02): Make execution terminated
<pmake -d build          -h> => non-zero return: 512
Build failed

LowLevelMahn · 2024-10-13T11:16:59Z

OWNOWGML=1 works on Tumbleweed - not dosbox gets called - not build error

jmalak · 2024-10-13T11:17:02Z

Yes, it is possible.
bellow is minimal steps to reproduce call to DOSBOX with minimal OW build.

Build minimal build system from scratch on Linux
It builds a few tools necessary for test sample, not need repeat if already done

configure OW build environments for build host
run sh build.sh preboot
cd bld/watcom
run builder boot
cd ../bmp2eps
run builder boot
cd ../..

reproduce call to DOSBOX by

cd docs/ps
run wmake hbook=c_readme

if need repeat then cleanup docs/ps by

run wmake clean

then you can repeat call to DOSBOX by wmake command above

LowLevelMahn · 2024-10-13T11:36:58Z

Yes, it is possible.
bellow is minimal steps to reproduce call to DOSBOX with minimal build.

works!

any idea how to see exactly the call to dosbox - to get a minimal example

jmalak · 2024-10-13T11:46:21Z

setup OWWGMLDEBUG=1 it should show DOSBOX Window and wait for EXIT command to continue

anyway I found out simpler example

Build minimal build system from scratch on Linux
It builds a few tools necessary for test sample, not need repeat if already done

configure OW build environments for build host
run sh build.sh preboot

reproduce call to DOSBOX by

cd docs/ps
run wmake hbook=cgdoc

if need repeat then cleanup docs/ps by

run wmake clean

then you can repeat call to DOSBOX by wmake command above

LowLevelMahn · 2024-10-13T11:50:07Z

i have found it

you set set SDL_VIDEODRIVER=dummy before calling dosbox

in open-watcom-v2/build/mif/wgmlcmd.mif line 75

that don't like stagings SDL2 - i'll try set SDL_VIDEODRIVER=offscreen

jmalak · 2024-10-13T11:57:00Z

Sorry I forgot how to see commands.

Change command by adding verbose value

wmake hbook=cgdoc verbose=1

jmalak · 2024-10-13T12:03:57Z

SDL_VIDEODRIVER=dummy
is legal value and works before on any platform

LowLevelMahn · 2024-10-13T12:05:42Z

SDL_VIDEODRIVER=dummy
is legal value and works before on any platform

i know - maybe its due to dosbox staging switch to SDL2 instead of SDL1 with dosbox vanilla

running dosbox-staging from console with

SDL_VIDEODRIVER=dummy dosbox

gives the same error

SDL_VIDEODRIVER=offscreen dosbox

works but not when i change that in the build/mif/wgmlcmd.mif

jmalak · 2024-10-13T12:43:54Z

offscreen is not driver, but init attribute
You need to comment out both set SDL_VIDEODRIVER=dummy lines

LowLevelMahn · 2024-10-13T12:44:55Z

i changed the wgmlcmd.mif line with =dummy into =offscreen - but that gets someway ignored?

then i did a ./clean.sh restarted the console an did

. ./my_setvars.sh
./build.sh preboot
cd docs/ps
wmake hbook=cgdoc verbose=1

still prints set SDL_VIDEODRIVER=dummy

jmalak · 2024-10-13T12:46:42Z

be careful there are 2 definitions you need to change both

LowLevelMahn · 2024-10-13T12:52:47Z

be careful there are 2 definitions you need to change both

found "both"

works with SDL_VIDEODRIVER=offscreen and commenting them out

LowLevelMahn · 2024-10-13T12:58:29Z

SDL_VIDEODRIVER=offscreen works also for Ubuntu,SDL1 using DOSBox version 0.74-3

jmalak · 2024-10-13T13:10:45Z

SDL_VIDEODRIVER=offscreen doesn't work for "pure" old DOSBOX
I get

dosbox -conf "/home/jiri/ow2a/build/dosbox.cfg"  -c "mount c \"/home/jiri/ow2a\"" -c "c:\docs\ps\wgmlb.bat"

Exit to error: Can't init SDL No available video device

Error(E42): Last command making (run_wgml;cgdoc.ps) returned a bad status
Error(E02): Make execution terminated

LowLevelMahn · 2024-10-13T13:13:36Z

it depends on the SDL1 or system ability

i try to find out what is compatible with SDL1 and SDL2 - dummy or none would be best

offscreen also does not work with WSL

jmalak · 2024-10-13T13:29:26Z

I submit change fe858df to try to use default video setup instead of dummy
It could help you with DOSBOX staging which is not fully compatible with "pure" DOSBOX

LowLevelMahn · 2024-10-13T13:31:24Z

that works - with poping up windows - but ok so far

jmalak · 2024-10-13T15:49:06Z

I am sorry but I must return DOSBOX setup back because we need to run DOSBOX on background without terminal.
It is reason for SDL_VIDEODRIVER=dummy that DOSBOX not need terminal any way.
As soon as some driver is used then it requires interactive session that doesn't exists.

If you want to use DOSBOX staging then you need to ask to fix it to work properly without terminal with SDL_VIDEODRIVER=dummy. It looks like they destroy this functionality.
We support standard DOSBOX 0.7x versions which are stable and support this mode correctly.

LowLevelMahn · 2024-10-13T17:28:03Z

I am sorry but I must return DOSBOX setup back because we need to run DOSBOX on background without terminal.

no problem - having poping up windows all the while is stressy or even not possible when not gfx is availabe

LowLevelMahn · 2024-10-15T10:51:42Z

thanks for all the help - i will add another Tumbleweed part and Windows builds part to the wiki - with all the infos i got now

jmalak removed the bug label Oct 13, 2024

LowLevelMahn closed this as completed Oct 15, 2024

SUSE Linux/Tumbleweed build doese not work #1339

SUSE Linux/Tumbleweed build doese not work #1339

Comments

LowLevelMahn commented Oct 11, 2024 • edited Loading

jmalak commented Oct 11, 2024

LowLevelMahn commented Oct 11, 2024 • edited Loading

jmalak commented Oct 11, 2024

LowLevelMahn commented Oct 11, 2024 • edited Loading

jmalak commented Oct 11, 2024

LowLevelMahn commented Oct 11, 2024

LowLevelMahn commented Oct 11, 2024

jmalak commented Oct 11, 2024

LowLevelMahn commented Oct 12, 2024 • edited Loading

jmalak commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024 • edited Loading

LowLevelMahn commented Oct 12, 2024 • edited Loading

jmalak commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024

jmalak commented Oct 12, 2024 • edited Loading

LowLevelMahn commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024 • edited Loading

LowLevelMahn commented Oct 12, 2024 • edited Loading

LowLevelMahn commented Oct 12, 2024

jmalak commented Oct 12, 2024 • edited Loading

jmalak commented Oct 12, 2024 • edited Loading

LowLevelMahn commented Oct 12, 2024

jmalak commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024 • edited Loading

jmalak commented Oct 12, 2024

LowLevelMahn commented Oct 12, 2024 • edited Loading

jmalak commented Oct 12, 2024

jmalak commented Oct 13, 2024

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024

LowLevelMahn commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024 • edited Loading

jmalak commented Oct 13, 2024

jmalak commented Oct 13, 2024

LowLevelMahn commented Oct 13, 2024 • edited Loading

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

LowLevelMahn commented Oct 13, 2024 • edited Loading

jmalak commented Oct 13, 2024

DOSBox version 0.74-3 Copyright 2002-2019 DOSBox Team, published under GNU GPL.

LowLevelMahn commented Oct 13, 2024 • edited Loading

jmalak commented Oct 13, 2024 • edited Loading

LowLevelMahn commented Oct 13, 2024

jmalak commented Oct 13, 2024

LowLevelMahn commented Oct 13, 2024

LowLevelMahn commented Oct 15, 2024

LowLevelMahn commented Oct 11, 2024 •

edited

Loading

LowLevelMahn commented Oct 11, 2024 •

edited

Loading

LowLevelMahn commented Oct 11, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

jmalak commented Oct 12, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

jmalak commented Oct 12, 2024 •

edited

Loading

jmalak commented Oct 12, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

LowLevelMahn commented Oct 12, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading

LowLevelMahn commented Oct 13, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading

LowLevelMahn commented Oct 13, 2024 •

edited

Loading

LowLevelMahn commented Oct 13, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading

LowLevelMahn commented Oct 13, 2024 •

edited

Loading

DOSBox version 0.74-3
Copyright 2002-2019 DOSBox Team, published under GNU GPL.

LowLevelMahn commented Oct 13, 2024 •

edited

Loading

jmalak commented Oct 13, 2024 •

edited

Loading