On Mon, Jul 4, 2011 at 4:15 PM, Jonas Maebe <jonas.ma...@elis.ugent.be> wrote: > This is virtually always caused by differences in the interface and > implementation definition of some routines. Examples of ways in which this > can happen: > a) inline routines: the body of the inline routine changes the interface > definition as far as the compiler is concerned > b) routines that are declared normally in the interface, but as "external" in > the implementation
Any more examples? There is no usage of inline nor external in my package / project combination (excluding the LCL, FCL and RLT, of course, but I guess that they can't be the cause of the problem). It seams like it would be excelent if the compiler could issue a warning when it decides that a unit has the interface / implementation problem and requires recompilation... Also curious is the intermittent nature of the problem. My solution was to add the path to the project options so that fpc could build the html package twice, but now I removed that path and it still works, even after rebuilding clean the LCL + all packages, which previously would fail. -- Felipe Monteiro de Carvalho _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
