[SOLVED] Don't understand buildfaq and make cycle lazarus / 3-General ---------------------------------------------------------------------- BigChimp · 2011-06-25 07:47 I'm extending http://forge.lazarusforum.de/projects/lazupdater Lazupdater with git support and install from scratch functionality (http://forge.lazarusforum.de/issues/118). Currently doing this on Windows but should be extended to Linux, OSX. The build faq, paragraph 2.2, suggests that you can use make cycle to bootstrap the FPC compiler with an old version. 1. Therefore, I'm downloading FPC 2.4.2 binary (latest stable 2.4 version I could get a binary package from) and placing it in a temp directory, e.g. c:\windows\temp 2. Extract GIT/SVN FPC into e.g. c:\development\fpc\source 3. cd c:\development\fpc\source 4. make cycle PP=C:\windows\temp\ppc386.exe Then I get make: *** No rule to make target `cycle'.  Stop. (make all does seem to work) What am I doing wrong? Is the buildfaq outdated and should I just use make all? Or should I use make all, and repeat with the newly generated compiler? Thanks. ---------------------------------------------------------------------- marcov · 2011-06-25 11:28 Quote from: BigChimp on June 25, 2011, 09:47:26 am Then I get make: *** No rule to make target `cycle'.  Stop. (make all does seem to work) What am I doing wrong? Is the buildfaq outdated and should I just use make all? Or should I use make all, and repeat with the newly generated compiler? The buildfaq needs an update, but all the stuff in it is still valid.  The problem is you are trying in the wrong directory. The examples in 2.2 all first descend to compiler/. So "make cycle" is in fpcsrc/compiler/ "make all" is in fpcsrc/(called making snapshots in the buildfaq), and this also calls cycle as the first part. ---------------------------------------------------------------------- BigChimp · 2011-06-25 11:50 Great, thanks for showing me the error of my ways gently. make cycle does indeed work in the source subdir. But if I understand you correctly, I wouldn't even need to do that, just make all PP=c:\bla\ppc386.exe and FPC would get bootstrapped (make cycle in the compiler subdir), then RTL/FCL would be compiled using the newly compiled compiler? That does simplify things! Thanks. ---------------------------------------------------------------------- marcov · 2011-06-25 15:30 Quote from: BigChimp on June 25, 2011, 01:50:53 pm But if I understand you correctly, I wouldn't even need to do that, just make all PP=c:\bla\ppc386.exe and FPC would get bootstrapped (make cycle in the compiler subdir), then RTL/FCL would be compiled using the newly compiled compiler? Correct. The whole shebang. Then another "install" step (e.g. to an empty dir), and you get pretty much the "bin" and "units" dirs as installed by a snapshot/release.  The buildfaq examples try to describe that. ---------------------------------------------------------------------- BigChimp · 2011-06-26 08:10 Right, thanks a lot!