[fpc-pascal] Re: compiling 2.6.1 from 2.4.5

Marco van de Voort marcov at stack.nl
Mon Mar 12 14:50:35 CET 2012


In our previous episode, Thierry B. said:
> >> So I just try your advice. Builds :
> >> - 2.6.0 from 2.4.5 : oops, not 2.4.4 but it is : OK
> >> - 2.6.1 from 2.6.0 : NOK : __missing_command_DATA2INC -b -s fppkg.cfg fppkg.inc fppkg
> >>
> >> same error, so there is something wrong with 2.6.1
> >
> > No. It means that you are trying to build it using only the 2.6.0 compiler binary, rather than with a complete 2.6.0 installation in your path. Only the latter is supported. The former usually works, but it may not due to source file time stamp variations.
> >
> OK, so now starting with 2.61 the proper way to build FPC is to always 
> add previous compiler /bin directory to PATH? (I mean in case we do not 
> have a regular build installed from a package manager)

2.6.1 is formally not a version that can be started with, since it is not a
release.

You don't fulfill the requirements of having the full last release (2.6.0)
installed. 

Nothing much changed except that the problems that you describe don't come
from changing requirements, probably when you cycled 2.4.5 either you did
have some complete release installed, or you were simply lucky (timestamps
not being skewed by rounding issues)

Again, bootstrapping from snapshots and just the release compiler binary,
while possible, is not supported, and requirements may vary, and are not
written down. It is more meant for knowledgable devels and distribution
builders, not an end-user subject.

Other such binaries that I know of are fpcres and fpcmake



More information about the fpc-pascal mailing list