Hi,

I come back to freepascal after one year and I wanted to build all versions from my already installed 2.2.5. Builds:

- 2.4.0 from 2.2.5 : OK
- 2.4.2 from 2.4.0 : OK
- 2.4.4 from 2.4.2 : OK
- 2.4.5 from 2.4.2 : OK
- 2.6.1 from 2.4.5 : NOK : __missing_command_DATA2INC -b -s fppkg.cfg fppkg.inc fppkg

I can see from http://wiki.freepascal.org/Fpcmake#Trouble_Shooting :

his happens when a tool required by the make process is not found. Remedy: Add the path to the tool as an option to make, like DATA2INC=/path/to/data2inc, for the tool data2inc

Well, why only for 2.6.1? data2inc is in every previously build freepascal /bin directory.

Thierry B

In our previous episode, Thierry B. said:

This is usually a difference between a formal release and a badly installed snapshot. Releases install data2inc, and the snapshot might not be fully installed.

The only guaranteed and supported way of compiling Free Pascal is to use the latest release. Thus you should build 2.6.0 with your 2.4.4 (not 2.4.5) and then build 2.6.1 using that 2.6.0.

Regards,
Sven

Thanks,

I believed that for this purpose the "fixes" branch was equivalent to the "release branch.
I always had troubles to /translate/understand this sentence from the freepascal "buildfaq" :

The only starting compiler that is guaranteed to work is the most

recent release compiler for that series [N→] [→N] E.g. For the 1.9.x series, even though 1.9.6 and 1.9.8 will probably work, the only guaranteed starting compiler is 1.0.10

Is this the same as you advice?

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

Thierry B

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.

Jonas

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)

In our previous episode, Thierry B. said:

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