Re: [9front] Re: [PATCH] game boy advance header target for 5l

[cinap_lenrek@felloff.net]

> I dont want to do relocation, I just want to know
> why external programs that only work under assumptions
> of how the a.out was linked are preferable to just
> having the linker output correct files.

Sorry, then i must have misundersood you.

> If everyone else is in agreement that this kind of header
> code should only be done in external programs, should that
> code also be moved to be external or deleted?

I do not see a need to be dogmatic about this at all
or force a decision.

I do not have any skin in this game nor do i have a gameboy.

Was just pointing out why an external tool would only solve
half the problem in this case. But i think we agree here.

A external tool made perfect sense for uimage as we want to
generate both an a.out (for debugger and /dev/reboot) and a
uimage for uboot. Linking is quite expensive compared to just
writing out a header and copying some data out of a file and
calculating a checksum.

For the gameboy rom image problem, my first guess would be to
just generate the header using the assembler and pass that
as the first object to the linker and have the linker geneate
headerless image.

--
cinap