OS: 64-bit Debian Stretch. When I was on 32-bit Debian Jessie there wasn't such problem, compilation was fast. The hardware is the same as before. The same goes for compilation command. Compilation command: fpc filename.pas -g -Cr. My systems is mixed, it allow execution and installation of both 32-bit and 64-bit applications. It seems that 99% of time takes linking. It seems that other languages (like C) aren't affected by such problem. Compilation of *.lpr files in Lazarus works fine.You must have something criminally wrong because it compiles on a humble RPi in less than 0.1
This code took 52 second to compile:
BEGIN write('Hello, cruel world!'); END.
That should allow you to get a better idea about what is taking so long.Thanks for the idea. Does it work by principle "do a thing and only then report that you did it?". If yes, then it's all fault of "[0.156] Linking helloworld" step. Everything else works momentally. Although I said already that it's linking that slows everything down.
The compiler usually first writes what it is going to do and only then does it. To really be sure it's the linking step, you could compile with -Cn and then execute the generated ppas.sh. That shell script will then just execute the linking step.
I am having the same issue on my office PC, windows 7, textmode IDE 3.0.4, a hello world program taking 5 seconds for linking. The issue only appeared a few months ago, and I am fairly certain it is related to the virus scannerFirstly, this is called an antivirus monitor, not an antivirus scanner. Secondly I don't use antivirus monitor because I use Debian Linux.
According to "time" execution of ppas.sh took about 3 seconds. Probably much slower than it should be for helloworld, but it's clearly isn't reason of the main slowdown.Indeed.
When I compiled with -Cn I also used -va for detailed log. It seems that primary candidates for bottleneck are "[41.254] Searching file /usr/bin/ld... found" andNot sure. This means that searching for /usr/bin/ld took less than 0.001 seconds. The primary candidate for the bottleneck would be before that.
"[41.254] Using util /usr/bin/ld"
Also, did you switch to a different type of file system when going from 32 to 64 bit?Nope.