Interesting! But my report was based on my development machine, a PowerBook G4.
Apparently the special instructions are not used or not causing a problem
because it also runs fine on the NAS.
-
Please excuse the shortness of this mail which was sent from my mobile phone.
If necessary, I
Hi,
On Tue, 5 Dec 2017, tobiasgie...@gmail.com wrote:
> I think the only problem is with fpmake, which doesn't include
> FPC_ABI_EABI for powerpc 32-bit processors.
>
> My use case is running my software on a Synology DS-413 NAS, which has a
> PowerPC processor. It's only a few years old.
Hi,
I will check it but the app really runs fine now after changing only
FpFtruncate, and
also FppRead and FppWrite (which nobody seems to use anyway). These are the
occurrences of {$ifdef FPC_ABI_EABI}.
I think the only problem is with fpmake, which doesn't include FPC_ABI_EABI for
powerpc
In our previous episode, Tobias Giesen said:
> I just filed a bug report about FpFtruncate passing the parameters
> incorrectly to the
> system. For example, setting a file size to $D would cause the file to have
> the size
> $D 000D. Apparently the conditional define FPC_ABI_EABI would fix
Hello,
I just filed a bug report about FpFtruncate passing the parameters incorrectly
to the
system. For example, setting a file size to $D would cause the file to have the
size
$D 000D. Apparently the conditional define FPC_ABI_EABI would fix it, but
what
other impact does it have?
I
