Re: [cc65] Re: Problem with generating o65 files

Hi!

On Fri, Jan 21, 2005 at 10:36:34AM +0100, Spiro Trikaliotis wrote:
> Now, I'm making progress, but I am stuck again. Not only do I get an
> error message
>
>    co65.exe: Warning: Operating system option without data found

Just ignore it for now. As I've found from your feedback, support for other
o65 files besides the cc65 is unfinished, and I'm currently not sure, how to
handle the case that generates the warning.

>   PP_READWRITE_DATA = XXX
[...]

That's because exports were not handled.

> Furthermore, if I try to compile any of the generated files, I get the
> following message:
>
>    1541.s(35): Error: Unexpected trailing garbage characters

That's no wonder, because the generated files are not valid:-)

> For all three files, the line cited is the one which defines
>
>    .segment        "ZEROPAGE", zeropage
>
> so, I believe the ", zeropage" is the thing which the assembler does not
> like. Ok, I can confirm this, because removing the trailing ", zeropage"
> results in the (expected) error message

The syntax for segments has changed, but co65 was not updated. Using cc65
modules, one does not run into this problem, because the zeropage is handled
differently, so no one noticed.

I will send you a diff for co65 in private mail which fixes the zeropage
segment and exports problem. However, I cannot guarantee that this is the last
problem, you will run into. See below.

> BTW: You once told me to use the Lunix ld65 configuration file as a
> starting point. Where do I find that one? From ld65-5.html#ss5.10, it
> seems they could be found in a platform-specific package, but there is
> no one for Lunix. Ok, I found it in the sources, but this statement in
> the docs is misleading, at least.

The reason for this is that lunix is not really a fully supported target. The
compiler is able to generate output for Lunix, but the necessary support files
(even the startup file) are not part of cc65. This means that I cannot test
anything at all, and there is a high chance that things will break when parts
of the compiler package change, because I cannot bring the Lunix target in
sync. So the paragraph you are citing from the docs is not really appropriate
in the given case. Targets that have platform specific packages do contain the
linker config in the doc subdirectory as stated.

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.