errors when compiling from trunk lazarus / 13-General ---------------------------------------------------------------------- soerensen3 · 2020-03-02 23:15 Hi, a lot of times when I try to compile Lazarus from trunk I encounter errors. Is this normal behaviour or is it just my config files. I'm using fpcupdeluxe. I read it saves all changes made to the sources and reapplies them again so i reverted all local changes but still could not compile. This happens a lot so I always have to fall back to stable when it happens, which again causes a lot of head aches with incompatible packages. ---------------------------------------------------------------------- trev · 2020-03-03 00:40 I don't have any problem compiling Lazarus trunk ... very occasionally the resulting Lazarus has issues. I download the Lazarus source with svn: Code: [Select]// If checking out the source the first time cd /Users/trev/lazarus-src svn checkout https://svn.freepascal.org/svn/lazarus/trunk . // If updating after first checkout cd /Users/trev/lazarus-src svn up and use the following script to compile it on macOS: Code: [Select]#!/bin/sh cd /Users/trev/lazarus-src make distclean all LCL_PLATFORM=cocoa CPU_TARGET=x86_64 bigide ---------------------------------------------------------------------- marcov · 2020-03-03 11:57 Errors is not very descriptive, but if the error is an exception in FPC with a traceback with "spill" in it, yes, I have that too from time to time. ---------------------------------------------------------------------- soerensen3 · 2020-03-03 21:46 Ok i my fault. I meant compiler errors as in some function in some unit changed and another unit is not changed accordingly. So the question should rather be is it a common problem that a revision is not compileable because of some patch or is the problem on my side. It usually happens when in fpcupdeluxe I update lazarus from trunk and it does not compile. When I do it again another day it might work again. Today it is working again with manually calling "make distclean all". I can not reproduce it anymore. @marcov: I had an exception like this only once.