[fpc-devel] Revisiting MacOS for PPC (and possibly 68K)

Sven Barth pascaldragon at googlemail.com
Mon Dec 10 17:11:47 CET 2012

Am 10.12.2012 17:05, schrieb Mark Morgan Lloyd:
> Sven Barth wrote:
>> Am 10.12.2012 12:15, schrieb Mark Morgan Lloyd:
>>> I'm currently cross-compiling the MacOS RTL for PPC on a PC. I've 
>>> fixed some trivial issues that had crept in since this was last 
>>> maintained, some of which affect other targets, but am stuck at the 
>>> errors below.
>>> /usr/local/src/fpc/fpc-trunk/compiler/ppcXppc -Ur -Tmacos -Ppowerpc 
>>> -XPpowerpc-macos- -Xr -Ur -Xs -O2 -n -Fi../inc -Fi../powerpc -FE. 
>>> -FU/usr/local/src/fpc/fpc-trunk/rtl/units/powerpc-macos -dpowerpc 
>>> -dRELEASE  -Us -Sg system.pp
>>> text.inc(1789,14) Warning: Implicit string type conversion from 
>>> "AnsiString" to "UnicodeString"
>>> text.inc(2013,44) Warning: Implicit string type conversion with 
>>> potential data loss from "UnicodeString" to "AnsiString"
>>> system.pp(481,2) Warning: User defined: To be implemented - using 
>>> GetProcessInformation???
>>> system.pp(571) Fatal: Internal error 2003090901
>>> Fatal: Compilation aborted
>>> make[2]: *** [system.ppu] Error 1
>>> make[2]: Leaving directory `/usr/local/src/fpc/fpc-trunk/rtl/macos'
>>> Allowing that system.pp ends at line 570, I presume that something 
>>> after  line 481 is confusing the compiler. Any suggestions would be 
>>> appreciated.
>> On a second note: Is that assembler you are using a GNU assembler? If 
>> so then it might be better you use the "link on target" feature of 
>> FPC ("-st") as the GNU assembler is not supported for Mac OS...
> Yes, and noted (should that be grafted into a makefile?). Presumably 
> I'm not quite at that stage yet.
You can pass "CROSSOPT="-st"" to the call of make.

You are nearly at that stage though as the compiler has already parsed 
the unit, generated the assembler code tree and now is about to output 
the assembly file (system.s) and call the assembler. And while the step 
of outputing the assembler file is currently failing for you the last 
step which will immediately follow will then fail as well...


More information about the fpc-devel mailing list