[Pkg-pascal-devel] compiling packages as user (and autopkgtest)

[Abou Al Montacir]

On Sat, 2018-11-17 at 08:47 +0100, Abou Al Montacir wrote:
> > ...
> > > > that $(lazbuild A) fails to find (and) compile package B, even if
> > > > package B was compiled just before. It seems the logic of lazbuild
> > > 
> > > So you compiled package B and then try to compile package A that depends
> > > on B, isn't it?
> > 
> > Well, I just compile ALL packages found in the lazarus tree (see
> > https://salsa.debian.org/pascal-team/lazarus/blob/experimental/debian/tests/
> > build-lpk-lpi#L20
> > The order is determined by the find. But in several cases it seems that
> > package B is compiled before A indeed.
> I've ran the script (on my 1.8.4 installation) and I've got this:
> ...
> There are only 2 unexpected failures.
> I've ran the first one manually:
> ...This package looks for Windows unit, I don't think it will compile under
> Linux.
> The second one compiled correctly manually. So I suppose it was depending on a
> package that was compiler after it in the list.
After multiple runs I've come to the conclusion that each run there is a
different list of failures.Looking at the output I can notice:An unhandled
exception occurred at $00005560290FC3F3:EAccessViolation: Access
violation  $00005560290FC3F3  $0000556029134365  $0000556029138427  $00005560291
39631Trying to reproduce manually on the package does not work and the package
compiles correctly. I can think about bug#902888. 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.
> > > Did you install the package B first? Please refer to --add-package
> > > command line option of lazbuild.
> > 
> > ...
> > 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?
> 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.
It seems we don't need to install any package. See above....
> 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.
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.
-- 
Cheers,
Abou Al Montacir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20181117/0eed1adb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20181117/0eed1adb/attachment.sig>