The following error occurred when compiling current trunk version (34361) on win64,…
Update your Free Pascal.

Mailing lists / lazarus / 2011-12
14 messages · 7 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
The following error occurred when compiling current trunk version (34361) on win64,…
Update your Free Pascal.
The following error occurred when compiling current trunk version (34361) on win64,…
The following error occurred when compiling current trunk version (34361) on win64, issued as: make bigide OPT="-dUseCHMHelp"
Compiling lazregions.pas
lazregions.pas(39,37) Error: Identifier not found "TFPCustomRegion" lazregions.pas(39,37) Error: class type expected, but got "<erroneous type>" lazregions.pas(52,14) Error: There is no method in an ancestor class to be overr
idden: "TLazRegion.GetBoundingRect:<record type>;" lazregions.pas(53,14) Error: There is no method in an ancestor class to be overr
idden: "TLazRegion.IsPointInRegion(LongInt,LongInt):Boolean;" lazregions.pas(69,14) Warning: An inherited method is hidden by "TLazRegionWithC
hilds.IsPointInRegion(LongInt,LongInt):TLazRegionWithChilds;" lazregions.pas(74,1) Fatal: There were 4 errors compiling module, stopping Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `D:/lazarus/lcl'
make: *** [lcl] Error 2
Using FPC 2.7.1
In lazregions.pas there are several ifdef's on the fpc version that go upto 2.6. Since you use 2.7.1 they fail. Add 2.7 to the ifdefs or use fpc 2.4.4/ 2.6.0. Officially lazarus compiles only what latest fpc release version.
Ludo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20111222/4e920bdb/attachment.html>
22.12.2011 19:28, Ludo Brands ?????:
But not officially lazarus compiles with svn trunk _head_ .
The following error occurred when compiling current trunk version (34361) on win64,…
And LATEST(!!) trunk.
Regards,
Sven
The following error occurred when compiling current trunk version (34361) on win64, issued as: make bigide OPT=?-dUseCHMHelp?
Compiling lazregions.pas
lazregions.pas(39,37) Error: Identifier not found "TFPCustomRegion" lazregions.pas(39,37) Error: class type expected, but got "<erroneous type>" lazregions.pas(52,14) Error: There is no method in an ancestor class to be overr idden: "TLazRegion.GetBoundingRect:<record type>;" lazregions.pas(53,14) Error: There is no method in an ancestor class to be overr idden: "TLazRegion.IsPointInRegion(LongInt,LongInt):Boolean;" lazregions.pas(69,14) Warning: An inherited method is hidden by "TLazRegionWithC hilds.IsPointInRegion(LongInt,LongInt):TLazRegionWithChilds;" lazregions.pas(74,1) Fatal: There were 4 errors compiling module, stopping Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `D:/lazarus/lcl'
make: *** [lcl] Error 2
Using FPC 2.7.1
Regards,
Marcelo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20111222/c883b60e/attachment-0001.html>
And LATEST(!!) trunk. Sven
Latest trunk fails on 2.7.1. Trunk used to work on 2.7.1 (e.g. 32573). That's a trifle inconvenient on a platform where there have been CG fixes since 2.4/2.6.
Mark Morgan Lloyd wroteLatest trunk fails on 2.7.1. Trunk used to work on 2.7.1 (e.g. 32573). That's a trifle inconvenient on a platform where there have been CG fixes since 2.4/2.6.
Lazarus subversion works in the very latest FPC trunk. Your fpc 2.7.1 is too old and no longer supported. You need to update your FPC.
The most common cause for this kind of requirement are changes in fcl-image, which prompts Lazarus to update itself to better use the new fcl-image capabilities. I think we are almost done with fcl-image changes, I can only think only about WindowOrg as a basic missing part in fcl-image now.
Latest trunk fails on 2.7.1. Trunk used to work on 2.7.1 (e.g. 32573). That's a trifle…
It does not fail, because otherwise the 2.7.1 snapshots in ftp://ftp.hu.freepascal.org/pub/lazarus/snapshots/ would not have been created (also I tested it manually on my system). You need to use at least revision 19852 of FPC otherwise the compilation will indeed fail. [and if you compile Lazarus on a 64-bit system with a 64-bit compiler that was created using a 32-bit compiler you need to pay attention to this bug: http://bugs.freepascal.org/view.php?id=20947 ]
Regards,
Sven
OK, but I'm simultaneously trying to find out why I can't compile 2.7.1 on SPARC Solaris, and am not finding the overall combination easy. More on that one elsewhere, although I'm up to my eyes in "holiday" scheduled maintenance at the moment.
So you have specific problems with compiling a recent 2.7.1 on SPARC? Then I would suggest you to ask on fpc-pascal or fpc-devel list whether someone else (including me) knows what your problem is. Maybe I should also take the time over the holidays to set up a small test system on QEMU ^^
Regards,
Sven
I can assure you that I have every intention of doing so :-)
[NOT expecting discussion here, but in brief I've got 2.4.4 working here on SPARC Solaris 8 and 10. Ludo got Lazarus working on x86 Solaris 10 and I followed his lead for SPARC. 2.7.1 on SPARC Solaris 8 and 10 worked a few weeks ago but something's broken since I was last able to put time into it. 2.7.1 OK on SPARC Linux but 2.4.4 not OK due to (now-fixed) CG issues, this caused problems at one point when 2.7.1 wouldn't compile with the slightly older version on my system).]
Currently tied up with server maintenance. Happy Midwinter Solstice everybody.
On Fri, Dec 23, 2011 at 9:12 AM, Mark Morgan Lloyd Lazarus subversion works in the very…
Were the changes done as <=2.6.0 vs >2.6.0
or are they done <=2.6 >2.6 ?
In the latter case, it will be a problem when such changes get merged to 2.6.1
Update your Free Pascal. Felipe Monteiro de Carvalho
Yep, that caught me !! A fresh compiler solved the problem. BTW, still using FPC 2.7.1, generated from trunk revision 19883.
Thanks, Felipe.
-----Mensagem Original-----
Were the changes done as <=2.6.0 vs >2.6.0 or are they done <=2.6 >2.6 ? In the latter…
I check 2.6.x at the moment. But changing the code to react only to 2.6.0 as opposed to 2.6.x is trivial
I didn't know the changes were scheduled for inclusion in 2.6.1 when I wrote the defines, one cannot support both possibilities at the same time. If they are going the best would be to merge all fcl-image changes.