Referring to http://www.freepascal.org/develop.var is there a reason why the "Fixes to 2.6.x" section gives a URI for fixes_2_2 ?

What's correct in this context- branches/fixes_2_6/ or branches/fixes_2_6_0/ ?

I'm trying to find a 2.6.1 that will compile Lazarus 1.0. Yesterday's daily snapshot fails with

Compiling intfgraphics.pas
intfgraphics.pas(634,49) Error: Identifier not found "TTiffIDF"

Is there a specific revision number that is known to be OK for this? I'm trying to do notes for somebody off-list, and there's a code-generation patch in 2.6.1 that's needed for SPARC.

Mark Morgan Lloyd hat am 5. September 2012
um 11:38 geschrieben:

fixes_2_6

See compiler/version.pas

I'm trying to find a 2.6.1 that will compile Lazarus 1.0. Yesterday's daily snapshot fails with

Yesterday a feature was backported to fpc. I updated lazarus. Todays snapshot should work.

Mattias

In our previous episode, Mark Morgan Lloyd said:

Referring to http://www.freepascal.org/develop.var is there a reason why the "Fixes to 2.6.x" section gives a URI for fixes_2_2 ?

Take your pick:
1. it is just an example
2. lazy webadmins
3. it is fixed in svn

Is there a specific revision number that is known to be OK for this? I'm trying to do notes for somebody off-list, and there's a code-generation patch in 2.6.1 that's needed for SPARC.

Mattias already answered that. The last two days 100+ revs were merged, mostly fpdoc related though, but also fcl-web and fcl-image.

fcl-db is on schedule for the next time I have time (probably the weekend)

Unfortunately I still get the same problem with a freshly-downloaded fpcbuild.zip (2.6 + fixes) and Lazarus 1.0 from svn. Working on x86 Linux.

> Compiling intfgraphics.pas > intfgraphics.pas(634,49) Error: Identifier not found "TTiffIDF" > intfgraphics.pas(634,15) Warning: An inherited method is hidden by

"TLazReaderTiff.DoCreateImage(<erroneous type>);"

> intfgraphics.pas(737,1) Fatal: There were 1 errors compiling module,

stopping

> Fatal: Compilation aborted

It sounds as though the best course would be if I waited a couple of days for the dust to settle.

The object of the exercise is to try to get a few lines related to Lazarus 1.0 at the bottom of
http://wiki.lazarus.freepascal.org/Lazarus_on_Solaris since Lazarus/FPC has been mentioned elsewhere as a good development environment for Solaris.

Mark Morgan Lloyd wrote on Wed, 05 Sep 2012:

Current FPC 2.6.1 will never be able to compile Lazarus 1.0, since Lazarus 1.0 was released before those changes went into 2.6.1. If you are talking about some kind of Lazarus 1.0.x fixes branch, then you'll probably have to wait a while before the change to accommodate that recent FPC 2.6.1 commit (which should probably be documented on http://wiki.freepascal.org/User_Changes_Trunk, since it apparently breaks existing code) has been merged from Lazarus trunk into this fixes branch.

Jonas

Thanks Jonas, noted. I'm going to step back a little and build a clean 2.6.0 from an fpcbuild .zip, build a Lazarus 1.0, and then see how many issues still give obvious problems. Mantis suggests that the issues I reported in the latter part of last year were fixed in 2.7.1, but so far my experience of 2.6.0 on SPARC suggests that either they were backported to that release or I applied the patches manually (I usually keep better notes of this than I appear to have done in this case).

I've been spending too much time using the trunk of both projects, on account of trying to push various other things I'm doing forwards.

Mark Morgan Lloyd wrote on Wed, 05 Sep 2012:

Unfortunately, mantis is seldom updated when changes are merged back these days. I used to do that for all changes merged back by anyone, but it's become too much work (and it's also much more work to figure out this information afterwards compared to immediately updating mantis after merging, since in the latter case you don't have to look up whether something was merged back and if so, in which revision).

Jonas

Thanks Jonas. Below are SPARC-specific issues that I'm aware of, this is for the benefit of anybody from the Solaris/OpenIndiana communities and I'm most definitely not trying to criticise project management.

0020072: Floating-point register allocation for doubles [Noted by Marco as being backported.]

0020397: Variant returns wrong Int64 value on SPARC. [Marked as fixed in 2.7.1, don't see any problem in 2.6.0.]

0020153: Bus error when compiling trunk (18976) on SPARC etc. [Ditto.]

Practical experience suggests that Lazarus 1.0 + FPC 2.6.0 is OK (the program that showed up the above appears to work as expected). Residual issues:

0020396: Signed 32-bit multiplication raises an overflow exception if result -ve [Still in 2.6.0 and 2.6.1. OK in 2.7.1.] For the time being, don't use -Co or the equivalent Lazarus project setting.

0020240: Arithmetic exception when compiling fp+gdb on SPARC [Possible duplicate of 0020265: Compiler crashes with SIGFPE, which is marked as fixed in 2.7.1 but might still be a problem in 2.6.0.] For the time being, don't use the FP IDE's libgdb interface.