The OpenWatcom C++ compiler at www.openwatcom.org has a work-in-progress Linux port but there is no ebuild for it. Having an ebuild could encourage more Gentoo involvement in that port. An ebuild is currently being worked on - see http://www.openwatcom.org/index.php/Installing_Open_Watcom_on_Linux and http://www.openwatcom.org/index.php/User:SadKo
Created attachment 161462 [details]
Open Watcom ebuild created by Dron
Thanks to Andrey 'Dron' Valyaev (http://mdf-i.blogspot.com/) for creating alternative gentoo open watcom ebuild.
- you inherit eclesses, which are never used
- use examples, not samples, source not sources
- Do not create $P in src_unpack(), set $S
- $D needs to be quoted
- Missing the license test file attached
Created attachment 161568 [details]
Sybase Open Watcom Public License version 1.0
Created attachment 161574 [details]
OpenWatcom 1.7.1 ebuild
This ebuild is okay?
(In reply to comment #4)
> Created an attachment (id=161568) 
> Sybase Open Watcom Public License version 1.0
License is OSI-approved -
-- build report --
ebuild from 2008-07-28T19:37 works for me.
I created overlay dir `/usr/local/portage/custom/sys-devel/openwatcom` and used `ebuild openwatcom-1.7.1.ebuild` as per
http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds - just needed to `ebuild openwatcom-1.7.1.ebuild digest` and emerge.
Keywords are set to 'x86' so no unmasking/keywording required for me.
and I can successfully `owcc hello.c` and `./a.out`
-- warning: wildly off-topic for this bug report --
The PDF at http://www.scitechsoft.com/pdf/openwatcom_crossbebug_QNX_whitepaper.pdf (Sep 2006 - needs registration) suggests the debugger will handle gcc-built apps: "Open Watcom Debugger is already functional for debugging GNU gcc generated code for x86 Linux targets. The remote debugger can run natively on Linux host with either a text-based window for console modes or an X client window for GUI desktop modes."
Compiling with `owcc -g2 hello.c` and then `wd a.out` gives me a fabulous ncurses debugger that looks just like it did back in '95 on DOS32 :-) This just might be a viable toolchain.
FWIW, Debian seem to have decided the licensing is not sufficiently Free for them:
Can't find any benchmarks comparing OW with GCC on Linux, though. Anyone?
Is openwatcom-1.7.1.ebuild a final release?
Can I take it to make an OpenWatcom mirror?
openwatcom-1.7.1.ebuild emerges fine for me and openwatcom works fine.
Created attachment 206293 [details]
Openwatcom 1.7.1 and 1.8.0 ebuilds
Created attachment 206649 [details, diff]
Recognize AMD64 as acceptable architecture
Recognize X86_64 in addition to 386 to orrect "Unknown CPU architecture" error in wmake/c/mglob.c
I'm trying to build openwatcom-1.8.0 on an AMD64 and have encountered 2 problems.
#1 - "Unknown CPU architecture" error in wmake/c/mglob.c. I've submitted a patch for the problem.
#2 - wlink segfaults, which kills the build (see below). Will post more info when I have it.
wlink op q format dos com op nodefault file code386.obj name xcode386.tmp disable 1023,1080
Error(E42): Last command making (xcode386.tmp) returned a bad status
Error(E02): Make execution terminated
The openwatcom-1.8.0 ebuild has a QA notice because of writeable and executable .sym files:
* QA Notice: The following files contain writable and executable sections
* Files with such sections will not work properly (or at all!) on some
* architectures/operating systems. A bug should be filed at
* http://bugs.gentoo.org/ to make sure the issue is fixed.
* For more information, see http://hardened.gentoo.org/gnu-stack.xml
* Please include the following list of files in your report:
* Note: Bugs should be filed for the respective maintainers
* of the package in question and not email@example.com.
* !WX --- --- opt/openwatcom/binl/codeview.sym
* !WX --- --- opt/openwatcom/binl/dwarf.sym
Created attachment 305281 [details]
tested on Hardened Gentoo x86
emerge --info : https://bugs.gentoo.org/attachment.cgi?id=304777
Created attachment 315245 [details]
full build log
Looks like 1.9.0 version have trouble with building, log attached
seems like it overwrites CC and CFLAGS
Created attachment 321816 [details]
openwatcom live ebuild
Attaching live ebuild, which builds ok, because all needed fixes pushed to the upstream.
app-emulation/virtualbox is using openwatcom now instead of dev86. Time to get this into portage.
Since old OpenWatcom seems dead there is a fork of it https://open-watcom.github.io/open-watcom/
It looks very promising and it would be nice to have it in the tree instead of the old one.
See for yourself:
This is V2 Fork of Open Watcom suite of compilers and tools
Bellow is list of main differences against Open Watcom 1.9
New 2-phase build system, OW can be build by platform native C/C++ compiler or by itself
Code generator properly initialize pointers by DLL symbol addresses
DOS version of tools now support long file names (LFN) if appropriate LFN driver is loaded by DOS
OW is ported to 64-bit hosts (WIN64, Linux X64)
Librarian support X64 CPU object modules and libraries
RDOS 32-bit C run-time compact memory model libraries are fixed
Resource compiler and Resource editors support WIN64 executables
OW text editor is now self containing, it can be used as standalone tool without any requirements for any additional files or configuration
Broken C++ compiler pre-compiled header template support is fixed
Many C++ compiler crashes are fixed
Debugger has no length limit for any used environment variable
(In reply to Anton Kochkov from comment #19)
> Since old OpenWatcom seems dead there is a fork of it
> It looks very promising and it would be nice to have it in the tree instead
> of the old one.
> See for yourself:
> This is V2 Fork of Open Watcom suite of compilers and tools
> Bellow is list of main differences against Open Watcom 1.9
> New 2-phase build system, OW can be build by platform native C/C++
> compiler or by itself
> Code generator properly initialize pointers by DLL symbol addresses
> DOS version of tools now support long file names (LFN) if appropriate
> LFN driver is loaded by DOS
> OW is ported to 64-bit hosts (WIN64, Linux X64)
> Librarian support X64 CPU object modules and libraries
> RDOS 32-bit C run-time compact memory model libraries are fixed
> Resource compiler and Resource editors support WIN64 executables
> OW text editor is now self containing, it can be used as standalone tool
> without any requirements for any additional files or configuration
> Broken C++ compiler pre-compiled header template support is fixed
> Many C++ compiler crashes are fixed
> Debugger has no length limit for any used environment variable
The project was being actively developed since, and the mainstream bug to track the possible upcoming release is here https://github.com/open-watcom/open-watcom-v2/issues/487