Re: [cc65] Forced imports by linker config

From: "Ullrich von Bassewitz"; on Friday, Nov. 12, 2010; 09:52 AM -0500
>
> A few of the easier examples:  ....
>
> Or, we can place a memory area inside a buffer that is defined
> in an assembly module:
>
> ----------------------------------------------------------------
> drivebuf.s:
          .segment        "DRIVERCODE"
>         DriveBuffer:    .res    256
>         .export         DriveBuffer
>         .export         DriveBufferSize = .sizeof (DriveBuffer)
> ----------------------------------------------------------------
> SYMBOLS {
>     DriveBuffer:     type = import, addrsize = absolute;
>     DriveBufferSize: type = import, addrsize = absolute;
> }
> MEMORY {
>     RAM:         file = %O,           start = $800, size = $D000;
>     DRIVEBUFFER: file = "driver.bin", start = DriveBuffer, size = \
>         DriveBufferSize;
> }
> SEGMENTS {
>     DRIVERCODE: load = DRIVEBUFFER, type = ro;
> }
> ----------------------------------------------------------------

That looks like a circular dependency!  DriveBuffer's address comes from
DRIVERCODE's address, which comes from DRIVEBUFFER's address, which
comes from DriveBuffer, which comes from DRIVERCODE, which comes from
...

Or, did you mean to put DriveBuffer in some other segment?

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