#Makefile Made!!!
3 messages in this thread
Mike:
I found my own problem with that makefile. When linking the last object
file, getfile.o, I kept getting an error that some data was out of range. I
think it had a number like 24. It listed the pc offset, but I long ago
forgot how to read the assembler dump (shamed).
The result is that the link completes, the code works, but the makefile
never completes! I recompiled that last module alone with the -md switch.
That did it! No error message on the link, and I now got ol' Porky to do
his thing after the Comm is all put together.
One last problem unsolved: Did you ever get around to figuring out why
I can't get the F keys tied in with the Quik Fix commands?
Thanks
Regards Tom
Um, its generally not a good idea to mix large and small data model in the
same program. It can be done, but the potential for running into problems
is pretty big. If you're compiling one module for large-data, I'd
generally recommend compiling all of them for that model (and linking with
the appropriate libraries, of course 8-), unless there's a significant size
or speed problem with that.
I'm looking into your z.opt problem – its definitely strange!
-Mike
Mike:
Thanks for the warning. The module in question is a tad wierd. With
Dan James' Comm code, he incorporated the old Heath file requester, rather
than troubling himself to reinvent the wheel. (Khalid was probably not
even *born* when this was written. hee-hee) This is rather exotic, both
in its selection of variable names, and comments. It compiles fine, like
the other dozen modules, but the linker squawks about <24>Data being out of
reach at pc=44c. Big Whoop! I compiled that module with the -md switch,
and all seems OK. I won't argue with you. I'll recompile. I see NO
reason for the linker to complain. Neither does Lint. But who are we to
argue with a Linker? 😎
Regards Tom