[fpc-devel] Porting FPC to IBM zArch

Mark Morgan Lloyd markMLl.fpc-devel at telemetry.co.uk
Thu Jul 25 15:12:19 CEST 2013


Sven Barth wrote:
> Am 25.07.2013 12:10, schrieb Mark Morgan Lloyd:
>> Sven Barth wrote:
>>> On 24.07.2013 16:36, Bernd Oppolzer wrote:
>>>> Then I built the RTL for linux, which also worked successfully, as far
>>>> as I saw,
>>>> but when compiling with -Tlinux, I now get the following message:
>>>
>>> How did you build it? Building the RTL for Linux should be (assuming 
>>> that your FPC source is at c:\fpc)
>>>
>>> cd c:\fpc
>>> make crossall CPU_TARGET=i386 OS_TARGET=linux 
>>> CROSSBINDIR=C:\path\to\linux\binutils BINUTILSPREFIX=i386-linux-
>>>
>>> BINUTILSPREFIX could also be something different or empty (then the 
>>> option should be "BINUTILSPREFIX="), it depends on how your 
>>> assembler/linker for Linux is prefixed.
>>>
>>> Once that worked you can install the compiler using
>>>
>>> make crossinstall CPU_TARGET=i386 OS_TARGET=linux 
>>> INSTALL_PREFIX=c:\wherever\fpc\should\be\installed
>>
>> Is it possible to "ask" the makefile for the true names of the 
>> supported targets?
>>
> Huh? What do you mean with "true names" and "supported targets"?

You're telling him that it's possible to build using ...CPU_TARGET=i386 
OS_TARGET=linux but where do those come from? Without being told by a 
developer or without referring to fully updated documentation, how does 
somebody know to use "i386" rather than "x86", or whether it should be 
"mips" or "mipseb"?

I can see that there's a MAKEFILETARGETS list in the makefile, which 
obviously goes slightly further than I'm asking in that it shows the 
valid combinations (i.e. somebody trying to build for powerpc + os2 is 
severely out of luck). But something like a "targets" target would be 
useful.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]



More information about the fpc-devel mailing list