<html><head></head><body bgcolor="#ffffff" text="#2e3436" link="#2a76c6" vlink="#2e3436"><div><br></div><div>On Sat, 2018-11-17 at 08:47 +0100, Abou Al Montacir wrote:</div><blockquote type="cite"><div><br></div><blockquote type="cite"><pre>...
<blockquote type="cite">
<blockquote type="cite">
that $(lazbuild A) fails to find (and) compile package B, even if
package B was compiled just before. It seems the logic of lazbuild
</blockquote>
So you compiled package B and then try to compile package A that depends
on B, isn't it?
</blockquote>
Well, I just compile ALL packages found in the lazarus tree (see
<a href="https://salsa.debian.org/pascal-team/lazarus/blob/experimental/debian/tests/build-lpk-lpi#L20">https://salsa.debian.org/pascal-team/lazarus/blob/experimental/debian/tests/build-lpk-lpi#L20</a>
The order is determined by the find. But in several cases it seems that
package B is compiled before A indeed.
</pre></blockquote><div>I've ran the script (on my 1.8.4 installation) and I've got this:</div><pre>...</pre><pre><br></pre><div>There are only 2 unexpected failures.</div><div>I've ran the first one manually:</div><pre>...</pre><pre>This package looks for Windows unit, I don't think it will compile under Linux.</pre><div><br></div><div>The second one compiled correctly manually. So I suppose it was depending on a package that was compiler after it in the list.</div></blockquote><div>After multiple runs I've come to the conclusion that each run there is a different list of failures.</div><div>Looking at the output I can notice:</div><pre>An unhandled exception occurred at $00005560290FC3F3:</pre><pre>EAccessViolation: Access violation</pre><pre> $00005560290FC3F3</pre><pre> $0000556029134365</pre><pre> $0000556029138427</pre><pre> $0000556029139631</pre><pre></pre><div>Trying to reproduce manually on the package does not work and the package compiles correctly. I can think about <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902888">bug#902888</a>. It is not exactly the same description but maybe have similar cause although the stack trace don't have the same deepness. I may need to recompile lazbuild with debug symbols, and this make me notice that we don't have -dbg packages.</div><blockquote type="cite"><div><br></div><blockquote type="cite"><pre><blockquote type="cite">
Did you install the package B first? Please refer to --add-package
command line option of lazbuild.
</blockquote>
...</pre><pre>
So how do I figure out which packages I need to add to the command line
automatically? Can you maybe change the file linked above for me?
</pre></blockquote><div>In fact you don't need to add a package each time. Lazarus uses a kind of list of compiled and installed packages that is stored in a cache. Once you add a package it will remain added until you remove it. However I don't see how to remove it using lazbuild. It seems you need to use the IDE for that.</div></blockquote><div>It seems we don't need to install any package. See above.</div><div>...</div><blockquote type="cite"><div><br></div><div>According to help of lazbuild, you may want to use -r instead of -B but I'm not sure it will do it and it will cause compilation time to increase as every package will be recompiled.</div></blockquote><div>I think we don't need neither -B nor -r. We just need to use lazbuild without any flag. If the package is already build, we don't need to build it again.</div><div><div style="white-space: normal;"><span><pre><pre>-- <br></pre>Cheers,
Abou Al Montacir</pre></span></div></div></body></html>