Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
On 25/03/2010 15:04, Graeme Geldenhuys wrote: Hi, I'm using r15061 checked out via svn from 'fixes_2_4' branch, and trying to compile it with FPC 2.2.5 under 64-bit linux. /opt/fpc_2.2.5/bin/ppcx64 -Ur -Ur -Xs -O2 -n -Fi../inc -Fi../x86_64 -Fi../unix -Fix86_64 -FE. -FU/opt/fpc_fixes_svn/src/rtl/units/x86_64-linux -Cg -dx86_64 -dRELEASE ../unix/baseunix.pp bunxovlh.inc(74,26) Fatal: Syntax error, : expected but identifier NSET found Fatal: Compilation aborted make[7]: *** [baseunix.ppu] Error 1 make[7]: Leaving directory `/opt/fpc_fixes_svn/src/rtl/linux' $ make all PP=/opt/fpc_2.2.5/bin/ppcx64 I had the exact same thing about an hour ago. Seems you need at least fpc 2.4.0 to compile trunc. 2.2 doesn't seem to know out params Martin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
In our previous episode, Martin said: $ make all PP=/opt/fpc_2.2.5/bin/ppcx64 I had the exact same thing about an hour ago. Seems you need at least fpc 2.4.0 to compile trunc. 2.2 doesn't seem to know out params (yes it does, but probably only in Delphi mode) As always, only the last release is guaranteed to work as starting compiler. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
On Thu, 25 Mar 2010, Graeme Geldenhuys wrote: On 25 March 2010 17:32, Marco van de Voort mar...@stack.nl wrote: 2.2 doesn't seem to know out params (yes it does, but probably only in Delphi mode) I thought it strange too. I couldn't see a clear syntax error, and yes I have used out parameters in FPC before, so didn't think that could be the cause of the compiler problem. As always, only the last release is guaranteed to work as starting compiler. I thought FPC 2.2.5 was the last previous release, as FPC 2.4.1 is simply a point release to 2.4.0. We have no 'point releases'. By definition, releases always have even numbers as the last digit. 2.4.1 and 2.2.5 are therefor not releases. So 2.4.0 or 2.2.4 are releases. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
Graeme Geldenhuys schreef: As always, only the last release is guaranteed to work as starting compiler. I thought FPC 2.2.5 was the last previous release, as FPC 2.4.1 is simply a point release to 2.4.0. Anyway, using my previous version of 2.4.1 dated Jan 2010 did manage to compile the latest fixes branch correctly. Thanks Martin and Marco. Better get a 2.4.0 compiler binrary, because at some point in time using 2.4.1 might break too, as marco wrote above. Vincent ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
On 25 March 2010 21:00, Vincent Snijders vsnijd...@vodafonevast.nl wrote: Better get a 2.4.0 compiler binrary, because at some point in time using 2.4.1 might break too, as marco wrote above. I never delete my previous working compiler, until I have a new working compiler - so it shouldn't pose to much of a problem. But I thinking having a clean 2.4.0 as a backup is a good idea. I guess now I can delete 2.2.5 while I'm at it. -- Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
Graeme Geldenhuys schreef: On 25 March 2010 21:00, Vincent Snijders vsnijd...@vodafonevast.nl wrote: Better get a 2.4.0 compiler binrary, because at some point in time using 2.4.1 might break too, as marco wrote above. I never delete my previous working compiler, until I have a new working compiler - so it shouldn't pose to much of a problem. But I thinking having a clean 2.4.0 as a backup is a good idea. Your current working compiler 2.4.1 could possibly not work to compile your next 2.4.1. Then you need a 2.4.0 to compile 2.4.1. Vincent ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] fixes branch r15061 unable to compile - syntax error
In our previous episode, Graeme Geldenhuys said: Better get a 2.4.0 compiler binrary, because at some point in time using 2.4.1 might break too, as marco wrote above. I never delete my previous working compiler, until I have a new working compiler - so it shouldn't pose to much of a problem. But I thinking having a clean 2.4.0 as a backup is a good idea. I guess now I can delete 2.2.5 while I'm at it. After every full release I extract the starting compiler and rename it to ppcrel and put it in the path. That way I can always cycle by adding FPC=ppcrel. Having a fixed name for the starting compiler helps. The download wary can use the bootstrap compiles from ftp://ftp.hu.freepascal.org/pub/fpc/dist/2.4.0/bootstrap/ (thought they are more meant for automated build systems like FreeBSD ports) ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
