Possible bug with linker? #1359
Replies: 2 comments
-
Oh it's my incompetence. The quotation marks are setting it off. That probably shouldn't happen, but whatever. |
Beta Was this translation helpful? Give feedback.
-
Sorry, you have incorrectly configured Open Watcom
why you use absolute path instead tools name only? |
Beta Was this translation helpful? Give feedback.
-
Okay, so I've made a really complicated batch make script. Surprisingly despite my complete inexperience, it seems to mostly work, up until it gets to the linker.
Here is the script and the test bed. Keep in mind this is very much trial and error, so there's a couple things left to iron out that I definitely haven't noticed yet.
My inputs to the script are as follows:
%WATCOM%\binnt\wcc386.exe
%WATCOM%\binnt\wlink.exe
%cd%\CompileFolder
THIS NEEDS TO BE AN EXISTING FOLDER.%WATCOM%\h;%WATCOM%\h\nt
Now, let me walk you through how the linker script is formed. You can find this under the section :link. The first part of the script is immutable and looks like this currently:
Outside of nt_win supposedly not existing which is very weird, there are no issues with this section. The problem arises when I first try to use the autogenerated file list. This list is generated with a for loop, and every file is presented in 8.3 shorthand. In the current file incarnation, it looks like this:
This on paper would work. These objects absolutely exist. Hell, the command that's used to get these objects,
dir /b /s *.obj
, can ONLY list existing .obj files. However, the linker decided that they do not exist, given this output:I have no idea what the hell is happening and I'm not sure whether to file a bug report or not, because it could literally just be my incompetence.
Beta Was this translation helpful? Give feedback.
All reactions