[Nasm-bugs] [Bug 3392615] watcom updates

[noreply-nasm at dev.nasm.us]

https://bugzilla.nasm.us/show_bug.cgi?id=3392615

Ozkan Sezer <sezeroz at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #411739|0                           |1
        is obsolete|                            |

--- Comment #6 from Ozkan Sezer <sezeroz at gmail.com> ---
Created attachment 411786
  --> https://bugzilla.nasm.us/attachment.cgi?id=411786&action=edit
patch #1: build updates for watcom

(In reply to H. Peter Anvin from comment #5)
> So, config/unconfig.h also does other things, specifically it defines a
> bunch of things (mostly at the end of the file.) The whole point of
> unconfig.h is to not have to replicate those autoconf-generated macro
> definitions manually, causing continual breakage.
> 
> Therefore, unconfig.h needs to be included after the rest of the
> configuration
>  In the case configure is used, it happens to be in the same file; that is
> only because I haven't found a way (yet) to make autoconf generate multiple
> files (although now when I think about it perhaps autogen.sh could split the
> file for clarity.)
> 
> Since I don't have a working Watcom setup anymore, it's really important
> that any patches get fully implemented and tested before I pick them up, so
> I need you to undo that hunk of the patch and test it before I can apply it.

I removed the hunk changing unconfig.h inclusion: it builds for os/2, and
the resulting exes are identical without that hunk, so good.

> Finally, I am curious what your motivation for using Watcom is; is there any
> platform where it is still relevant?

I can easily cross-compile to os/2 on linux, for example: there is no way
of doing that using gcc toolchains.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.