Open watcom f77 - make file problems

  • Thread starter Thread starter eddyq
  • Start date Start date
  • Tags Tags
    File
AI Thread Summary
The discussion revolves around issues encountered while using Watcom 1.9 to build a simple project. The user faced multiple make errors when attempting to compile a file containing just a CALL EXIT and END. The errors were traced back to the use of the dollar sign ($) in file names, which led the makefile to misinterpret it as the beginning of a macro name. This confusion resulted in invalid macro name errors during execution. The solution was to remove the dollar sign from the file names, which resolved the compilation issues, allowing the project to compile successfully.
eddyq
Messages
8
Reaction score
0
I loaded Watcom 1.9. I built a simple project and added a simple file with just a CALL EXIT and END. But it gives a bunch of make errors. Does anyone know what is going on?

--- make files ---
W:\1830\port\test>type test.mk
project : W:\1830\port\test\test.exe .SYMBOLIC

!include W:\1830\port\test\test.mk1

W:\1830\port\test>type test.mk1
!define BLANK ""
W:\1830\port\test\TRBL$.obj : W:\1830\port\test\TRBL$.FOR .AUTODEPEND
@W:
cd W:\1830\port\test
wfc386 TRBL$.FOR -d2 -q -dep

W:\1830\port\test\test.exe : W:\1830\port\test\TRBL$.obj .AUTODEPEND
@W:
cd W:\1830\port\test
@%write test.lk1 FIL TRBLtest.exeobj
@%append test.lk1
!ifneq BLANK ""
*wlib -q -n -b test.imp
@%append test.lk1 LIBR test.imp
!endif
!ifneq BLANK ""
@%append test.lk1
!endif
*wlink name test d all sys nt op m op maxe=25 op q op symf @test.lk1


W:\1830\port\test>


--- output ---
cd W:\1830\port\test
wmake -f W:\1830\port\test\test.mk -h -e
W:\1830\port\test\test.mk1(2): Error(E08): Invalid macro name ()
W:\1830\port\test\test.mk1(2): Error(E08): Invalid macro name ()
W:\1830\port\test\test.mk1(7): Error(E08): Invalid macro name ()
Error(E02) Make execution terminated
Execution complete
 
Technology news on Phys.org
I think the problem is the $ characters.

In a makefile you can define a "macro variable" by saying something like
Code:
SOURCE = one.f two.f three.f
and then reference it by saying
Code:
wfc386 ${SOURCE}
which would be is expanded into the command
Code:
wfc386 one.f two.f three.f
When you say things like
Code:
W:\1830\port\test\TRBL$.obj,
I guess Make thinks the $ is the start of a macro name, and then can't make sense of the "."

Sorry, but I don't use watcom so I can't guess what you are actually trying to do here.
 
You hit the nail on the head ... I removed the $ and it compiles OK now.

Thanks
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
I tried a web search "the loss of programming ", and found an article saying that all aspects of writing, developing, and testing software programs will one day all be handled through artificial intelligence. One must wonder then, who is responsible. WHO is responsible for any problems, bugs, deficiencies, or whatever malfunctions which the programs make their users endure? Things may work wrong however the "wrong" happens. AI needs to fix the problems for the users. Any way to...

Similar threads

Back
Top