[Lazarus] Lazarus SVN build "stucked" to TFPCSourceCache.Update after ran

Thierry Bothorel thierry.bothorel at gmail.com
Tue Sep 28 13:55:55 CEST 2010


Vincent Snijders a écrit :
> 2010/9/27 Thierry Bothorel <thierry.bothorel at gmail.com>:
>   
>> Hi,
>>
>> since some days  after successfully building Lazarus from svn, I can't
>> run it on my Ubuntu 64 bit system : here is the outpout :
>>
>> Adding "--pcp=~/.lazarus" as a parameter
>> Adding "--scp=~/.lazarus" as a parameter
>>     
>
> Why are the primary and the secundary config directory the same. Data
> is copied from secundary config directory to primary config directory,
> and I can imagine that you create a endless loop, if they point to the
> same directory.
>
> Vincent
>   
OK I understand, but this has not caused me troubles before (~ 6
months). Why I did that. I have several Lazarus installations. A
"regular" one installed from :
deb http://www.hu.freepascal.org/lazarus/ lazarus-stable
and some others in my home directory.

Previously I ran Lazarus installation, build from latest source, without
any parameter, and others more "stable" with something like :
startlazarus --pcp=~/.lazarus-stable

But this cause me lots of troubles when running just :
startlazarus --pcp=~/.lazarus

when I believed deleting ~/.lazarus was enough, before I  understand it
use environment file for *regular" lazarus :

startlazarus
TLazarusManager.Run starting
/home/thierrybo/Sys/local/opt/lazarus_FPC_svn/lazarus ...
TMainIDE.ParseCmdLineOptions:
  PrimaryConfigPath="/home/thierrybo/.lazarus"
  SecondaryConfigPath="/etc/lazarus"
<-------------------------------------------


So I added

--scp=~/.lazarus to avoid this. This used to work until now. I have another build using svn code from 1 month ago, without any problem. My regular installation use also the two identical --pcp and --scp parameters.

Thierry B.






More information about the Lazarus mailing list