Current build for v2 - installer crashes upon copying files

[ekatus]

Current build. Installer crashes on Linux x64 (i5, 16G, Ubuntu)
Memory access error.

Selective install, only installing packages for DOS. Same with full install.

[jmalak]

It is known bug.
as workaround you can use 32-bit installer and ignore message about no space.

[ekatus]

This indeed did the trick. However, one minor thing: target OS is DOS, host OS is Linux. Headers are installed under ../h, however, script for setting up the environment let INCLUDE point to ../lh. After having fixed that, some samples compiled and linked nicely. Thanks for your support. Regards Michael

…

Am 10.04.2026 um 01:52 schrieb Jiří Malák ***@***.***>: jmalak left a comment (open-watcom/open-watcom-v2#1606) <#1606 (comment)> It is known bug. as workaround you can use 32-bit installer and ignore message about no space. — Reply to this email directly, view it on GitHub <#1606 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH2TAYX3VWAK7Z756MXPZ2T4VAZTDAVCNFSM6AAAAACXS7D3G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMJYGYZDENJSGI>. You are receiving this because you authored the thread.

[jmalak]

Sorry, Open Watcom is cross-compiler, that default configuration is always for native target which is host system.
INCLUDE variable is always setup (by installer) to headers subdirectory for native target not for selected target.
if you use Open Watcom for cross-compile (to target different then host) you must change INCLUDE variable to point to headers valid for your target temporarily see details about OW usage in Wiki and also specify target explicitly. It meens if you run OW tools without specifying target then native target is used and it uses INCLUDE variable for header (it must be native target).
By example if you compile for 32-bit Windows on Linux host then INCLUDE variable must point to $WATCOM/h even if default value is $WATCOM/lh. Such configuration should be part of build make file then you can build on any supported host without make file change (it is portable make file).

If you want cross-compile for single target only then you can change INCLUDE variable permanently, but then your make files or IDE projects are unportable, also Open Watcom CMake support is based on standard configuration. If you change INCLUDE variable permanently to non default value then result is unpredictable.