[fpc-devel] Fixes of FPC version 2.2.0

[Lee, John]

Yiannis, sorry about that - my fault. It's been a known problem for a while that will get fixed soon, we hope. 

I've mentioned the problem recently to Tomas, who 'owns' (or at least has fixed in past) the scripts that generate the fpc.zips (a few weeks ago).  The v22 fpc.zip (in snapshots/ source/v22) that I use for the v22 go32v2 and win32 snapshots (and for the base*.zip files which are just the compiler & RTL) is  stuck at r8445 and not tracking the latest v22 release(s) as it should.    

Not sure whether it's same or related issue with v2.3.1 not getting updated by my daily snapshot script, it builds fine here! 

Regards John  

> Subject: Re: [fpc-devel] Fixes of FPC version 2.2.0
> 
> 
> 
> On 12 Apr 2008, at 19:52, Yiannis Dondos wrote:
> 
> > I just wanted to ask if the current version 2.2.1 already includes  
> > all the fixes done since the release of 2.2.0.
> 
> No, it doesn't.
> 
> > The reason I am asking this is because I downloaded a very recent  
> > version of 'base_w32_v22.zip' from the FreePascal FTP 
> server (ftp://ftp.freepascal.org/pub/fpc/snapshot/fixes/i386-win32/ 
> > ) and I am almost certain that an issue reported as fixed 
> in 2.2.1 (http://bugs.freepascal.org/view.php?id=9275 
> > ) is still present.
> 
> The fix for that bug report has been merged back however, as 
> mentioned  
> in the bug report's history.
> 
> > Running 'fpc -i' reports version 2.2.1 (2008/04/12), but the  
> > 'readme.rev' file reports revision 8445, which is really old.
> 
> I don't know what's up with the Windows snapshots. The 2.3.1 one  
> hasn't been updated at all in ages, and apparently the 2.2.1 
> one isn't  
> properly updated either. It is probably indeed revision 8445, which  
> would explain why that fix isn't in the binary you downloaded.
> 
> 
> Jonas
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-devel
> 
> 

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.