WLINK command line error
Edward Schram
watcom. The linker script is complaining that in the following:
LINK_OPTS = name $*.hex SYS dos @CBoot.ord OUT HEX op m op maxe=25 op q
op symf fil
the SYS dos gives:
Warning! W1107: undefined system name: dos
The options were copied directly from the command line generated by the IDE.
Any ideas.
The linker is being called from C:\WATCOM\binnt
Hans-Bernhard Bröker
> the SYS dos gives:
>
> Warning! W1107: undefined system name: dos
You wouldn't by any chance have messed with the originally installed
wlink.lnk and wlsystem.lnk files, would you? Or maybe set a WATCOM or
WLINK_LNK environment variable to point to a non-standard version of it?
Edward Schram
not one in mine. I ran the install with default options and did not delete
it. It works in the IDE.
Ed
"Hans-Bernhard Br�ker" <bro...@physik.rwth-aachen.de> wrote in message
news:hd282o$mhc$1...@www.openwatcom.org...
Paul S. Person
<esc...@emcomms.com> wrote:
>The documentation says there should be one in the binnt dir, but there is
>not one in mine. I ran the install with default options and did not delete
>it. It works in the IDE.
1) If you are using Windows, it may show up as "wlink" with no
extension; it does this in XP. The reason for this is that ".lnk" is
the extension used for links. The icon should show a small arrow, just
like any other link file. Since it is not, in fact, a link file,
opening it for examination or editing can be a little tricky.
2) If it works under the IDE but not at the command line, then a
missing or incorrect path in an environment variable is the most
obvious suspect. "set | more" can be used to see if you have the binnt
directory in a path in an environment variable or not. IIRC, the IDE
was modified a while back to work even if the environment variable(s)
needed were not set when it was started.
If it is an environment variable problem, then there are at least two
options:
1) XP allows you to enter environment variables (right-click My
Computer, select Properties, select Advanced, push the Environment
Variables button. The environment variables you add (or modify) will
then be available in every command-line window you open (or every user
opens, depending on which box they are in).
2) Create a batch (or command) file to set the environment variables.
If you already have such a file that you use to otherwise set up your
environment (to move to the work directory, for example), then edit it
to set the environment variables.
A brief review of the documentation and the result of running my
command file suggests that the only new environment variable needed
should be "WATCOM", but that the host-specific directories need to be
added to "PATH". Note that both binnt and binw directories need to be
in the PATH -- and in that order.
Something like this should work for PATH (note that WATCOM must be
defined first!) in a batch (or command) file:
if "%DEFPATH%" == "" set DEFPATH=%PATH%
set PATH=%WATCOM%\binnt;%WATCOM%\binw;%DEFPATH%
unless you need something in binl or binp, in which case adding them
(after binw) should be pretty easy.
--
Here lies the Tuscan poet Aretino,
Who evil spoke of everyone but God,
Giving as his excuse, "I never knew him."
Hans-Bernhard Bröker
> The documentation says there should be one in the binnt dir, but there
> is not one in mine.
There probably is --- otherwise things wouldn't be working in the IDE.
%WATCOM%\binnt has only a wlink.lnk. There's only one wlsystem.lnk,
which is in %WATCOM%\binw.
There's a small chance the watcom environment variables are only
provided directly to the IDE, but not to whatever program session you
ran that makefile from. You'll have to debug that makefile yourself or
present a reproducible test case here, so others can help you with that.
Wmake -d -p output might help with that.