On 06 Oct 2012, at 20:14, Bernd wrote: > 2012/10/6 Jonas Maebe <jonas.ma...@elis.ugent.be>: > >> As has been mentioned a "few" times before, building FPC development >> versions has always been only supported when starting with the latest >> release. So: yes. > > I have never tried to build it on Launchpad servers before so I never > ran into this problem before and also google returns zero results for > the above error message.
Here google points to an FPC bug report as the first hit for that error message: http://www.google.be/search?q=%22Syntax+error,+%22:%22+expected+but+%22identifier+NSET%22+found%22 > Shouldn't this requirement be relaxed a bit so that it applies to last > stable branch instead of last minor release from the same branch? No. The reason is that it is simply impossible to test the functional correctness of the compiler with every possible svn revision from a particular branch before committing. This in turn means that supporting such scenarios would require a much larger investment of extra effort than the gain would justify ("Which svn revision did you use exactly as starting compiler? Oh, let me test. Ah yes, that one contained a bug that was fixed 3 revisions later. Let me add a workaround for this problem so that the current compiler can be bootstrapped using that particular revision"). > Isn't a minor version supposed to contain only fixes and not new > features? The error you get is not related to a new feature added in a fixes branch. It's caused by a source code cleanup, namely the removal a workaround to ensure that the code compiled with FPC 2.4.x/ Jonas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
