[Lazarus] Next FPC official release

ABorka fpc-devel at aborka.com
Fri Mar 4 20:36:28 CET 2011


On 3/4/2011 09:54, Vincent Snijders wrote:
> 2011/3/4 Vincent Snijders<vincent.snijders at gmail.com>:
>
>> If you use lazarus trunk svn head,with fpc trunk, you must use fpc
>> trunk *svn head* too. You did not, so your fpc 2.5.1 was too old.
>>
>
> So, if you update lazarus and compilation fails with fpc 2.5.1, you
> must update fpc too.
>
> Vincent

Just as a note, sometimes there can be additional problems with 
compiling FPC/Lazarus from SVN.
In both the case of FPC and Lazarus, sometimes a file or two gets moved 
between directories in the SVN directory tree and when someone does a 
"make clean..." after an "svn update..." the clean will not remove the 
older one from the install "units" directory and that can cause problems 
with future compiles, rebuilds.
Sometimes I got "checksum changed" error in a file at rebuild, sometimes 
packages did not compile, sometimes the rebuild did not find things, etc.

I just had this problem a few days ago when after 2-3 months I updated 
my FPC and Lazarus SVN from the trunk and tried to recompile both.

1. First of all I had to delete the target directories of the installed 
versions of FPC and Lazarus ("make clean" should do this but since the 
moved file is now in a new directory, it tries to delete it from the new 
place instead of from the old place therefore leaving the old one there)

2. Then I deleted all SVN checkouts for both FPC and Lazarus and checked 
them out again into a clean directory

3. I used the last stable FPC version to compile the new FPC trunk first 
(sometimes you can not successfully compile the latest FPC 2.5.1 with a 
one or two months old FPC 2.5.1)

4. Then I could compile the latest SVN FPC again with itself (compiled a 
2.5.1 with a 2.5.1 made by a 2.4.x....confused enough yet?)

5. Checked out Lazarus from SVN into a clean dir and built it, installed it

6. Removed the Lazarus settings directory before 1st start and then 
tested a rebuild from within Lazarus after setting the FPC dir in the 
environment menu. If this works without a problem, you can start adding 
the packages you use.

7. I had a problem with the latest stable Zeos 6.6.6 because it did not 
compile. After looking it up on the net, I found the necessary changes 
needed for Zeos to compile (changes were needed in one of the source 
files, ZClasses.pas) under FPC 2.5.1.

After a few hours I had a newly working FPC/Lazarus installation.
This all is not for the faint heart... but can be done.

AB







More information about the Lazarus mailing list