I am trying to build an FPC 3.0.0 + Lazarus 1.6.2 environment on a new Rpi3 with the latest Raspbian PIXEL.
I have come so far as to having compiled fpc 3.0.0 successfully and run its make install command to put the binaries in the expected places (all under /home/pi):

Now when I try to build Lazarus 1.6.2 from SVN sources I get this:

pi at rpi3-jessiepixel:~/dev/lazarus/1.6.2 $ time make bigide OPT=-dFPC_ARMHF FPC=/home/pi/bin/ppcarm
make -C packager/registration
make[1]: Entering directory
'/home/pi/dev/lazarus/1.6.2/packager/registration' /bin/rm -f ../units/arm-linux/fcllaz.ppu
/home/pi/bin/ppcarm -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -FE. -FU../units/arm-linux -dFPC_ARMHF -darm fcllaz.pas Free Pascal Compiler version 3.0.0 [2017/01/09] for arm Copyright (c) 1993-2015 by Florian Klaempfl and others (1002) Target OS: Linux for ARMHF
(3104) Compiling fcllaz.pas
Fatal: (10022) Can't find unit system used by fcllaz Fatal: (1018) Compilation aborted
Makefile:2702: recipe for target 'fcllaz.ppu' failed make[1]: *** [fcllaz.ppu] Error 1
make[1]: Leaving directory
'/home/pi/dev/lazarus/1.6.2/packager/registration' Makefile:3050: recipe for target 'registration' failed make: *** [registration] Error 2

real 0m0.171s

Why does it not find "unit system"?

I have searched for all files with a name system.* from ~/ and all that are found (rather many) are located inside the fpc source tree.

What could have happened here? Is there some extra option to add to the make command to tell it where the fpc sources are located?

I've had that issue, with different units, under Linux several times. A make clean before make bigide has solved the problem.

YMMV of course.

On 10/01/2017 12:48 pm, "Bo Berglund via Lazarus" <

wrote:

I am trying to build an FPC 3.0.0 + Lazarus 1.6.2 environment on a new Rpi3 with the latest Raspbian PIXEL.
I have come so far as to having compiled fpc 3.0.0 successfully and run its make install command to put the binaries in the expected places (all under /home/pi):

Now when I try to build Lazarus 1.6.2 from SVN sources I get this:

pi at rpi3-jessiepixel:~/dev/lazarus/1.6.2 $ time make bigide OPT=-dFPC_ARMHF FPC=/home/pi/bin/ppcarm
make -C packager/registration
make[1]: Entering directory
'/home/pi/dev/lazarus/1.6.2/packager/registration' /bin/rm -f ../units/arm-linux/fcllaz.ppu
/home/pi/bin/ppcarm -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -FE. -FU../units/arm-linux -dFPC_ARMHF -darm fcllaz.pas Free Pascal Compiler version 3.0.0 [2017/01/09] for arm Copyright (c) 1993-2015 by Florian Klaempfl and others (1002) Target OS: Linux for ARMHF
(3104) Compiling fcllaz.pas
Fatal: (10022) Can't find unit system used by fcllaz Fatal: (1018) Compilation aborted
Makefile:2702: recipe for target 'fcllaz.ppu' failed make[1]: *** [fcllaz.ppu] Error 1
make[1]: Leaving directory
'/home/pi/dev/lazarus/1.6.2/packager/registration' Makefile:3050: recipe for target 'registration' failed make: *** [registration] Error 2

real 0m0.171s

Why does it not find "unit system"?

I have searched for all files with a name system.* from ~/ and all that are found (rather many) are located inside the fpc source tree.

What could have happened here? Is there some extra option to add to the make command to tell it where the fpc sources are located?

Gordon Findlay wrote

I've had that issue, with different units, under Linux several times. A make clean before make bigide has solved the problem.

Well, in my case there was nothing to clean out since the source tree for lazarus had never been compiled. I ran make clean anyway but the problem for make bigide remains.

I suspect that while compiling lazarus it needs access to fpc sources as well and I don't know how to tell the system where they are. I have run make sourceinstall in the fpc source tree and it has deposited the sources inside ~/share, but where does one tell the system where it can find the sources?

For example there is no fpc.cfg file anywhere on my system, should it not have appeared when fpc was built?

No.

[...] For example there is no fpc.cfg file anywhere on my system, should it not have appeared when fpc was built?

No. You have to create it yourself. For example with the tool samplecfg.

Mattias

Mattias Gaertner wrote

> For example there is no fpc.cfg file anywhere on my system, should it > not have appeared when fpc was built? No. You have to create it yourself. For example with the tool samplecfg.

Just to complete this thread:
I used the tool samplecfg to make a new fpc.cfg and used it instead of my earlier one. Now the build system wors OK for Lazarus! Thanks.