Hi Gianfranco, On Tue, 2016-02-02 at 08:09 +0000, Gianfranco Costamagna wrote: > Source: fpc > Version: 3.0.0+dfsg-2 > Severity: serious > > > Hi, I open this ticket to discuss with you the regression I found on armel and > armhf platforms > in my hedgewars upload yesterday. > > I checked in a stretch clean pbuilder environment (both logs are attached), > and the testsuite runs correctly, > the only sensible change has been the fpc upgrade, and this is the reason for > this bug report. > > Test project /build/hedgewars-0.9.22-dfsg/obj-arm-linux-gnueabihf > Start 1: drillrockets_drill.lua > 1/6 Test #1: drillrockets_drill.lua ...........***Failed 0.92 sec > An unhandled exception occurred at $000C0300: > EInOutError: File not open > $000C0300 WriteLn, line 467 of /build/hedgewars-0.9.22- > dfsg/hedgewars/uUtils.pas > > > the strange thing is that the affected line seems rather simple: > procedure WriteLn(var f: textfile; s: shortstring); > begin > system.writeln(f, s) > end; > > > and the testsuite works perfectly on every other architecture, so I presume > this is an fpc specific regression. > (I can also ask to remove the hedgewars arm* architectures if needed) I could notice in the build log on sid the following warnings: hwengine.pas(626) Warning: "crtbeginS.o" not found, this will probably cause a linking failure hwen gine.pas(626) Warning: "crtendS.o" not found, this will probably cause a linking failure On the other hand these files seem to belong to libgcc-5-dev on my system $dpkg -S /usr/lib/gcc/x86_64-linux-gnu/5/crtbeginS.o libgcc-5-dev:amd64: /usr/lib/gcc/x86_64-linux-gnu/5/crtbeginS.o Can you please check if they are availables on the arm box you are using? The reason I think these warnings are related is that stdin/stdout are open by parent process so may be related to the C code initialization. I can probably be completely wrong, but let's check this first. -- Cheers, Abou Al Montacir
signature.asc
Description: This is a digitally signed message part