Hi,

All of this is of course of my own doing but is it expected?

I built and installed fpc trunk, just the 32-bit version. I have 3.0.4 32-bit, and for that release I also have the win32-win64 cross-compiler installed.

Having forgotten that I did not build the win32-win64 cross-compiler from trunk, I issued a
fpc -TWin64 -Px86_64 test.pas.
My path looks like C:\pp\bin\i386-win32;%oldpath%
(Trunk resides in C:\pp\bin\i386-win32)
And, as you can guess, the path to the 3.0.4 binaries is on %oldpath% And, lo and behold, fpc trunk executed the cross-compier from 3.0.4.

I can understand why.
But, is this desired behaviour?
A message that no cross-compiler for the current version of the compiler was installed would make a little more sense to me.

Well, yes. fpc executes what it find. This is how it works currently. The fpc executable has not to match with the real compiler executable.

PM Florian Klämpfl wrote

The fpc executable has not to match with the real compiler executable.

By design?
I find that a bit odd.

By design or not, the fpc executable holds no version information as of now, IIRC. Its functionality is very simple and there are almost no differences among the builds distributed with various FPC releases (the biggest difference probably being the list of supported architectures and the corresponding compiler names).

Obviously, it might be changed if needed. The question is if people really want such a warning. Note that it would work only if you rebuild the fpc executable as well, so I'm not sure if it would make any difference in your scenario.

Tomas

PM Tomas Hajny wrote

By design or not, the fpc executable holds no version information as of now, IIRC.

OK.

Obviously, it might be changed if needed. The question is if people really want such a warning.

Probably not, since I'm the first one to raise this ;-)

Note that it would work only if you rebuild the fpc executable as well, so I'm not sure if it would make any difference in your scenario.

Well, I would think that make all, followed by make install would generate a new fpc.exe as well.

Bart

Bart wrote

On Thu, Jan 3, 2019 at 7:06 PM Tomas Hajny wrote:

.
.

> Obviously, it might be changed if needed. The question is if people > really want such a warning. Probably not, since I'm the first one to raise this ;-)

That was indeed my thought as well. ;-)

In any case, _if_ doing it, I would do it by adding -Fu and -Fi pointing to the upper (i.e. compiler) directory to the Makefile rule for building the fpc executable, adding a possibility to pass the version information from fpc to the respective compiler by adding something like '-V?' + full_version_string to PPCCommandLine _if_ -V parameter has not been passed to the fpc executable already (it wouldn't make much sense otherwise), adding a new warning message to msg/errore.msg and adding handling of the new parameter to options.pas in the compiler directory. Obviously, it would only work for compiler versions having this functionality included, i.e. you couldn't safeguard against having really old versions invoked that way.

Yes, that should do that.

Tomas

That sounds like too much of a hassle.

Thanks for explaining.

I'll just try to remember to build and install the cross-compiler as well when I build trunk.

Bart