Errors when building FPC from source

[marcov]

Moderator notice: offtopic IRC messages and follow ups removed after complaints.

Please report off topic posts, don't reply to them.

[Aruna]

Oh this is totally unrelated and way off-topic but who are the core dev's for lazarus? And who are the core dev's for fpc?

To keep it simple:
- For Free pascal, see here
- For Lazarus, see here

Hey many thanks. 

But, having said that please also realize that there are tens if not hundreds of other people that contribute (or have contributed over the years) to both projects by various means (also to other associated projects such as f.e. the help).

It is just that they do not have (or do not want to have) the right to make certain decisions.

Alright, understood and respected.

I have a working laz-ide again but I want to start from scratch and document all the possible brick walls one can hit when doing this without the convenience of a package manager.

In case you want to do everything manually then there a few basic steps:
for FPC:
- get a bootstrap compiler (FPC-downloads, sourceforge)
- retrieve the source-code for the compiler version that should be build (git, gitlab, FPC-downloads, sourceforge)
- build the compiler with make using the bootstrap compiler
- install the freshly build compiler (make)
- configure the compiler for user specific setup (fpc.cfg) either manually or by using fpmkcfg
- test the compiler

for Lazarus:
- retrieve the source-code for the IDE version that should be build (git, gitlab, FPC-downloads, sourceforge)
- build the IDE with make using your freshly installed compiler
- install the freshly build Lazarus (make)
- make sure to set/configure the pcp directory
- optionally make a (menu) shortcut for your freshly build IDE
- test lazarus

Explaining each individual step is more complicated and depends on (and/or can depend on) platform, architecture, preferences, future plans and how someone want to have things setup.

The most easy way to install is ofc. using the package manager supplied by the OS and use their FPC and Lazarus packages. The downside of that solution is that there is hardly any upgrade path and/or room for personal preferences ad/or customization.

Thank you very much for this. I want to do this 'manually' for a reason, so 'I' learn how and what goes where and why? 

Have a look HERE and then HERE

Thank you for sharing and the shout-out. Man, you look wasted there (no offense). Please take good care of yourself !

No offence taken and yes I was quite out-of-it I just wanted to get the video done and sleep   I mean who starts testing a keyboard without turning on the power to the USB-hub first? In my defence I have done worse )

[Aruna]

Moderator notice: offtopic IRC messages and follow ups removed after complaints.

Please report off topic posts, don't reply to them.

My Apologies @marcov will not happen again!

[dbannon]

Aruna, here is my model for installing FPC and Lazarus, its chiefly about being quick and saving disk space. 

https://github.com/davidbannon/FPC_Laz_Install

I started doing this on VMs initially because I have so many and disk space is an issue. If you want FPC 3.2.4rc1, first you have to FPC322 to build it, and thats slow on a one cpu VM. My model is to have a tar of the compiled binaries and source on hand, untar it from #HOME and it ends up exactly where I want it, under $HOME/bin. Its very quick, resolves dependencies, installs a fpc.cfg. And easily deleted to save disk space before I close the VM.

My current script for downloading, building and configuring Lazarus is there too. I have been using these for awhile, but needed to do a lot of clean ups and sanity checks before going public.

I do not consider this, in any way, rival to FPCUPDELUXE, it is limited to -

• 64 bit Linux
• FPC 3.20, 3.2.2 and 3.2.4rc1
• Assumes a reasonably knowledgeable user, and one who wants to know where things

are !

• Has none of the fine detail or user friendlyness.

Right now, its a very convenient way to get the FPC release candidate at least.

Davo