[fpc-devel] Re: fpc-devel Digest, Vol 93, Issue 57
pascaldragon at googlemail.com
Mon Jan 30 19:40:43 CET 2012
On 30.01.2012 19:36, Mark Morgan Lloyd wrote:
> Sven Barth wrote:
>>> I would very strongly suggest cross-compile fpc on Linux/Windows
>>> using a version
>>> that emits, not gas assembler but 370 assembler. I will be talking
>>> about gas vs
>>> 370 assembler later. The assembler output can be in ASCII or EBCDIC
>>> as rvmartin
>>> said it's just a character encoding. The advantage is that you only
>>> need to
>>> upload a text file(s). Feed it into the OS assembler and link
>>> programs and you
>>> have a 370 load module.
>> Once a initial port to 370 has been made and the assembler output
>> generator is implemented (which means that the compiler can basically
>> generate 370 capable assembler files) this is rather easy as FPC can
>> generate "link on target" scripts (and AFAIK also "assemble on target").
> Assuming that the target operating system has any concept of an
> executable script. Steve's already told us that you can't generate a
> binary externally, and it might turn out that the compiler will have to
> generate a JCL (or comparable) deck which is then processed in some way
> on the target rather than being executed directly.
The link script does not need to be executable by itself. In the end it
would be sufficient to just include the commands in it that are needed
to assemble and link the final application and then execute these by
hand (in the worst case...).
More information about the fpc-devel