Hi!
Currently an fpc build start with building a new runtime with current fpc compiler. There can be a failure with this. For example: no such internal routine error if we try to build fpc 2.2.0 runtime with fpc 2.3.0. I think the right order is to start a build of new fpc-compiler with the current compiler and current runtime. And then start a building of new runtime with a new compiler.

The correct build order is always to start with the most recently released stable compiler.

You can never compile a 2.2.0 with a 2.3.x.

Michael.

The current runtime might be buggy and might not work for a new compiler.

2009/2/20 Michael Van Canneyt

The correct build order is always to start with the most recently released stable compiler. You can never compile a 2.2.0 with a 2.3.x.

But we can't compile 2.2.2 with a 2.3.0 too... It's a bad thing. And if start to compile fpc 2.2.2 (not runtime) by 2.3.0, then it is possible. By the way: why it is not corrected in sources of 2.2.2 piece of code where we write to a stream an enumeration constant? In 2.3.0 there is an assigment of this constants to a char arrary before writing such array to a stream.

2009/2/20 Florian Klaempfl

The current runtime might be buggy and might not work for a new compiler.

A wanted target: posibblity to compile an old compiler with a new one. If to start doing so from making a runtime then we can get a messages about problems with compiler functions. If to start from making a compiler then there can be all OK.

Why FPC is so unfrendly to itself? It have so many modes but can't compile old versions of itself.

SErgey Ya. KOrshunoff wrote

Why FPC is so unfrendly to itself? It have so many modes but can't compile old versions of itself.

Because code change and features change.

Compiling 2.2.2 with 2.2.0 makes sense, because that is the natural progression of source code and a product.

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

No, because the compiler itself also uses the run time library. So if it is compiled against an old run time library which contains certain bugs that are fixed in the current version, the resulting compiler may not work.

Jonas