search

open-watcom / open-watcom-v2

Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
Other
989 stars 162 forks source link

wdump fails to recognize linux386 object files #1213

Closed winspool closed 9 months ago

winspool commented 9 months ago

I tried wdump, but that failed:

wdump   bld/wcl/owcc/linux386/clcommon.obj 
Open Watcom Executable Image Dump Utility
Version 2.0 beta Jan 26 2024 12:25:26 (64-bit)
Copyright (c) 2002-2024 The Open Watcom Contributors. All Rights Reserved.
Portions Copyright (c) 1984-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See https://github.com/open-watcom/open-watcom-v2#readme for details.

bld/wcl/owcc/linux386/clcommon.obj does not have recognized format

That file is ok, and was successful used to link linux386/owcc.exe.

Even the linux file utility has a generic idea, what this object file is:

file     bld/wcl/owcc/linux386/clcommon.obj
bld/wcl/owcc/linux386/clcommon.obj: 8086 relocatable (Microsoft), "$OWROOT/bld/wcl/c/clcommon.c", 1st record data length 50, 2nd record type 0x88, 2nd record data length 8

(I shortened the path prefix to $OWROOT)

jmalak commented 9 months ago

you should read usage text of wdump or documentation what wdump purpose is.

winspool commented 9 months ago

you should read usage text of wdump or documentation what wdump purpose is.

Sure, i did that, before using it ("Eat your own dog food"):

I tried wdump -a with various files first, but for creating this report, i reduced the options as much as possible and used one of the affected object files as example.

There is no list, which parts of OpenWatcom are already supporting 64bit, and since orl is an essential low level part, i tried projects using orl first.