Lazarus now has a hard dependency on properly (and globally!) configured fppkg,
which requires fpc in your PATH.

Upside: Lazarus supposedly needs it for something to do with fpmake
dependencies, but it only really affects looking up paths of packages installed
via fppkg.
Downside: completely breaks the default Windows setup as well as any
self-contained installations (on any OS).

> b) how to avoid it?
Not currently fixable by a user.

However, as this only occurs when you have never run the fppkg client before,
you also cannot have any fppkg-managed packages, meaning the message is
perfectly safe to ignore. See attached patch, which restores the old logic.
Compiling *will* work even if fppkg is not configured (as it always has), as fpc
correctly uses fpc.cfg to find the package paths.