Lazarus

Installation => macOS / Mac OS X => Topic started by: lor on January 11, 2017, 03:30:59 pm

Title: Updating to Lazarus 1.6.2 - sourceforge sends wrong fpcsrc
Post by: lor on January 11, 2017, 03:30:59 pm
Downloading of fpcsrc-3.0.0-20151207-macosx.dmg, from sourceforge's lazarus 1.6.2 set of files, actually delivers fpcsrc-2.6.4, so Lazarus can't find the required source files, as it finds 2.6.4 in the place where 3.0.0 should be found. After installing the pkg  I was unable to find a folder for fpcsrc-3.0.0 anywhere.

I am able to compile pascal programs from the terminal and the compiler signs itself as 3.0.0, so the fpc compiler pkg was correct.

I have been using free pascal and lazarus for several years, so I am more or less familiar with the update process, but never had this problem before.

Is there an alternate location from which I can download the proper fpcsrc?
Title: Re: Updating to Lazarus 1.6.2 - sourceforge sends wrong fpcsrc
Post by: Thaddy on January 11, 2017, 05:55:15 pm
Is this really the case? Then it is a bug and should be reported on the bug tracker.
(I am only using Lazarus trunk and several versions of FPC)
[edit]
It is not strictly a bug: 1.6 was released with stable 2.6.4. But it should be updated anyway since fpc 2.6.4 is no longer maintained.
Title: Re: Updating to Lazarus 1.6.2 - sourceforge sends wrong fpcsrc
Post by: lor on January 11, 2017, 06:39:23 pm
Continued research on my part shows that my fpcsrc-2.6.4 was actually loaded back when I updated to the prior release of lazarus 1.6.

This means that the downloaded fpcsrc-3.0.0-20151207-macosx.dmg didn't put anything on my machine when the pkg was installed, or it put something somewhere  I don't recognize as appropriate. The date suffix on that file is suspicious as well.

BTW, I only upgraded because I've migrated to OS X 10.11 El Capitan.
Title: Re: Updating to Lazarus 1.6.2 - sourceforge sends wrong fpcsrc
Post by: lor on January 11, 2017, 06:42:59 pm
I will post a version of this question on bugtracker
TinyPortal © 2005-2018