I have installed Lazarus 2.0.12 and FPC 3.2.2 from sources retrieved from GitLab on a new Linux Ubuntu 20.04.3 LTS with the Cinnamon desktop environment.

After starting Lazarus I have used OLPM to add a number of packages I always use in my Lazarus setups.
But when doing the install and ending with the Lazarus rebuild it exits with the following error messages:

lazarus.pp(162,3) Note: Call to subroutine "function GetDebugger:TLazLogger;"
marked inline is not inlined
lazarus.pp(166,1) Error: resource compiler "fpres" not found, switching to
external mode

Same thing now happens if I exit Lazarus and start it again and then go to Tools/Build_Lazarus_with_Profile:_Normal_IDE

The lazarus.pp file is opened at this point, a file I have never touched.

First time I started Lazarus I only went to OnLinePackageManager in order to install my customary extra packages...

What can cause this and how do I solve it?

El 23/11/21 a les 11:12, Bo Berglund via lazarus ha escrit:

What can cause this and how do I solve it?

Did you try a "make all" or "make bigide" from the lazarus source directory (so it will build all its tools)?

Bye

Turns out that I was hit by the *same* problem 18 months ago and I got a solution then right here from Mattias Gaertner...

Look at the thread starting On Sun, 24 May 2020 22:21:31 +0200 titled: Lazarus on Ubuntu 18.04.4 via VNC cannot find utilities https://lists.lazarus-ide.org/pipermail/lazarus/2020-May/238019.html

But unlike that time VNC is *not* involved at all since I am now working inside a VMWare virtual macine with direct access to the desktop. Still the same problem occurs. And the solution also works.

Right now I have decided to document all details of FPC/Lazarus installation from sources on Linux since the move to GitLab disrupted all of my instrall scripts.

This "detail" has now entered my notes as well so it will be the last time I bother you with this.

A clean build usually solves such problems.

Juha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20211123/fc2c5891/attachment.html>

Juha Manninen wrote

A clean build usually solves such problems. Juha

Not really....

The problem was that in certain cases of Linux (Ubuntu?) the desktop file execution does not correctly pick up the $HOME/bin folder in path and that is where the binaries wind up.

Michel had the same problem and found this solution. (I should have quoted the actual solution in my last message rather than referencing the old thread... So I am doing it now below.)

The normal Exec line in the desktop file looks like this (on one single line):

Exec=/home/user/devel/lazarus/2.0.12/startlazarus
--pcp=/home/user/.lazarus_2.0.12 %f

And the modified line like this:

Exec=/bin/bash -l -c '/home/user/devel/lazarus/2.0.12/startlazarus --pcp=/home/user/.lazarus_2.0.12'

The first results in Lazarus *not* finding the binaries it needs, whereas the second makes sure to load the correct path into the session.

This will not be affected by any form of build.

Notice that when fpc and lazarus are built it is in a terminal session started by user and given the full path including to $HOME/bin So the standalone build process works whereas the lazarus session started from the Ubuntu menu using the desktop file only works with Michel's modifications.

I can confirm that the solution back in 2020 which worked then still works in this new environment today.

Bo Berglund wrote

Michel had the same problem and found this solution. (I should have quoted the actual solution in my last message rather than referencing the old thread... So I am doing it now below.)

SORRY! TYPO...
I meant Mattias Gaertner as the one who had the same problem and solved it!

Again too fast typing, it *WAS* Michael Van Canneyt who came up with the solution!
See here:
https://lists.lazarus-ide.org/pipermail/lazarus/2020-May/238022.html

Please disregard previous message!!