[fpc-pascal]GO32V2 EXE architecture...
kanzelsberger at rekt.umb.sk
Tue Jul 17 12:42:49 CEST 2001
Oh, that's not what I mean exactly...
That DXEGEN cannot convert .o file to .dxe because it doesn't understands
these symbols, I want to find way how to remove them (or do anything else)
so DXEGEN can successfully convert .o file...
Regards, Pavel Kanzelsberger
From: marcov at stack.nl [mailto:marcov at stack.nl]
Sent: Tuesday, July 17, 2001 12:30 PM
To: fpc-pascal at deadlock.et.tudelft.nl
Subject: Re: [fpc-pascal]GO32V2 EXE architecture...
> Well seems that i'll keep mailing here :-))
> I tried DXEGEN and it fails due to unrecognized symbols (which are FPC
> specific) in .o file...
> Is there any way how to remove them without editing .sw file?
> C:\DJGPP>dxegen lib.dxe _ADD lib.o
> ld -X -S -r -o dxe__tmp.o -Lc:/djgpp/lib lib.o -T dxe.ld
> Error: object contains unresolved external symbols (FPC_STACKCHECK)
> Error: object contains unresolved external symbols (INIT$$SYSTEM)
> Error: object contains unresolved external symbols
> Error: object contains unresolved external symbols (FPC_DO_EXIT)
I think you could simply try to create an empty assembler file that defines
those symbols for that, assemble
.globl FPC_STACKCHECK :
.globl INIT$$SYSTEM :
.globl FPC_INITIALIZEUNITS :
fpc-pascal maillist - fpc-pascal at lists.freepascal.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fpc-pascal