[Pkg-pascal-devel] cge FTBFS on powerpc/ppc64 and arm64 [Was Re: rebuilding with fpc 3.0.0]

Paul Gevers elbrus at debian.org
Wed Feb 3 19:42:17 UTC 2016


Hi Michalis,

cge FTBFS on powerpc and ppc64 (not new, see below) and arm64. On arm64
it looks like the cge code really needs to be ported to 64 bits on arm.
Are you interested into looking into that or should we consider arm64 as
not supported?

See:
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine&arch=arm64&ver=5.2.0-2&stamp=1454452069

On 28-11-15 00:41, Michalis Kamburelis wrote:
> Paul Gevers wrote:
>> Thanks for looking into this and thanks for the patch. Looking
>> slightly more into the failures on powerpc/ppc64 I get confused. I
>> thought I may have been doing something wrong in the packaging, but
>> the failure is in your makefile (that I patched) running your
>> mk_fonts.pas command. Do the errors make any sense to you?
>>
> 
> Not really... I see the error:
> 
>   cd src/fonts ;
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/«PKGBUILDDIR»/debian/tmp/tmp
> ./mk_fonts.sh
> 
>   texturefont2pascal: Expected 2 more parameters
> 
> ... but this should not happen. It certainly works on my system. I
> also tested CGE sources from Debian (from "apt-get source
> castle-game-engine"), since there's a small modification of
> mk_fonts.sh in Debian (to use ttf fonts installed globally in
> /usr/share/fonts/truetype/dejavu/...). It all works well here.
> 
> But I'm testing on x86_64 (amd64), and this also works according to
> https://buildd.debian.org/status/package.php?p=castle-game-engine . So
> something is different on powerpc, but I honestly have no idea what:)
> 
> Is it possible to get ssh access to a machine running powerpc/ppc64,
> for testing? I could probably debug the problem if I could run some tests:
> 
> - first, I would change "set -eu" to "set -eux" in mk_fonts.sh to see
> what parameters are passed by the shell. Maybe the bash on
> powerpc/ppc64 does something weird?

I added this to the Debian packaging so you now see that everything is
passed as expected. Still it fails.

> - if the shell parameters are correct, I would modify
> examples/fonts/texturefont2pascal.lpr to see what parameters does it
> "see". You can simply write the contents of Parameters array to
> inspect this. If the params are incorrect, you can check what is
> returned by FPC functions ParamCount, ParamStr --- maybe they are
> broken on powerpc/ppc64?

You now should have access for a while, still interested to try this out?

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-pascal-devel/attachments/20160203/521d1f20/attachment.sig>


More information about the Pkg-pascal-devel mailing list