Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2019-07

Compile fpc twice or only once during install?

4 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Bo Berglund

When I install FPC/Lazarus on new Linux systems I use a script I wrote several years ago. It is cofigured for the actual versions to install but otherwise it is self-contained.

What it does concerning fpc is:
- Get the tagged version of the sources from svn (typically 3.0.4)
- Get the seed compiler 3.0.0, which I have stored on my website
- Build all using the seed compiler
- Install sources etc.

Now I wonder if I should add a second "make all" after pointing to the newly built 3.0.4 such that the final result is fpc 3.0.4 built from sources compiled by itself?

Or is this superfluous?

Bo Berglund Developer in Sweden

Reply by email

Christo Crause
to Bo Berglund
Show quoted text 16 lines
When I install FPC/Lazarus on new Linux systems I use a script I wrote several years ago. It is cofigured for the actual versions to install but otherwise it is self-contained. What it does concerning fpc is: - Get the tagged version of the sources from svn (typically 3.0.4) - Get the seed compiler 3.0.0, which I have stored on my website - Build all using the seed compiler - Install sources etc. Now I wonder if I should add a second "make all" after pointing to the newly built 3.0.4 such that the final result is fpc 3.0.4 built from sources compiled by itself? Or is this superfluous?

AFAIK the make file cycle through the compiler build process 3, starting a new cycle with the compiler from the previous cycle. So no need to make all a 2nd time, it is implicit in the make file recipe.

Reply by email

Bo Berglund
to Christo Crause
Christo Crause wrote 10 lines
> Now I wonder if I should add a second "make all" after pointing to the > newly built 3.0.4 such that the final result is fpc 3.0.4 built from > sources compiled by itself? > > Or is this superfluous? > AFAIK the make file cycle through the compiler build process 3, starting a new cycle with the compiler from the previous cycle. So no need to make all a 2nd time, it is implicit in the make file recipe.

Thanks! No need to change the script then! :)

Bo Berglund Developer in Sweden

Reply by email

Sven Barth
to Christo Crause: AFAIK the make file cycle through the compiler build process 3, starting a new cycle with…

Christo Crause schrieb am Fr., 12. Juli 2019,
15:30:

Show quoted text 24 lines
On Fri, 12 Jul 2019, 14:19 Bo Berglund, wrote: > When I install FPC/Lazarus on new Linux systems I use a script I wrote > several years ago. It is cofigured for the actual versions to install > but otherwise it is self-contained. > > What it does concerning fpc is: > - Get the tagged version of the sources from svn (typically 3.0.4) > - Get the seed compiler 3.0.0, which I have stored on my website > - Build all using the seed compiler > - Install sources etc. > > Now I wonder if I should add a second "make all" after pointing to the > newly built 3.0.4 such that the final result is fpc 3.0.4 built from > sources compiled by itself? > > Or is this superfluous? > AFAIK the make file cycle through the compiler build process 3, starting a new cycle with the compiler from the previous cycle. So no need to make all a 2nd time, it is implicit in the make file recipe.

Correct. In fact it also throws in an additional WPOCYCLE (two compilations) to optimize the compiler further. ;)

Regards,
Sven

Reply by email