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

[Abou Al Montacir]

Hi Paul,
On Sat, 2018-11-17 at 21:35 +0100, Paul Gevers wrote:
> Hi
> 
> On 17-11-18 09:14, Abou Al Montacir wrote:
> > > > 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.
> 
> I don't understand what you mean? Or is that you think that we these
> compile errors are the real root cause of this all failing?
I just mean that the root cause of all these failures (at least on lazarus
1.8.4) is the access violation ( sigseg fault) that I've described in my
previous message. This is why I said see above.
Here I was just saying that I was wrong when I thought that we need to install
packages using --add-package.
> > > 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.
> 
> So you suggest to remove the -B I currently have in the test?
> 
> With the -B removed I get:
> The following files failed expectedly:
> /usr/lib/lazarus/2.0.0/components/lazreport/source/addons/lrOfficeImport/lr_of
> ficeimport.lpk
> /usr/lib/lazarus/2.0.0/components/lazreport/source/addons/lrspreadsheetexport/
> lrspreadsheetexport.lpk
> /usr/lib/lazarus/2.0.0/components/lazreport/source/addons/pdfexport/lazreportp
> dfexport.lpk
> /usr/lib/lazarus/2.0.0/components/lazreport/source/addons/ZeosDB/lr_zeosdb.lpk
> /usr/lib/lazarus/2.0.0/components/tachart/tachartbgra.lpk
As I explained in a previous mail, the failures are random access violations
exceptions on my laptop. If this is the case also on your side, then the number
of failures does not matter. These are just random failures.
> So that list is significantly shorter indeed, but it also doesn't seem
> to be doing any real compiling (the output dir /tmp/.lazarus is empty
> but for the environment file).
Yes because most of packages are already compiled, so no need to recompile them
again. The test is meant to test only non compiled packages, isn't it?
> Error messages (I check the first three and they makes sense to me)
> Error: (lazbuild) Broken dependency: lr_OfficeImport 0.0->laz_fpspreadsheet
> Error: (lazbuild) Broken dependency: lrSpreadSheetExport
> 0.9->laz_fpspreadsheet
> Error: (lazbuild) Broken dependency: lazreportpdfexport
> 0.9->pack_powerpdf (>=0.9.15)
> Error: (lazbuild) Broken dependency: LR_ZeosDB 0.2.2->zcomponent
> Error: (lazbuild) Broken dependency: TAChartBgra 1.0->bgrabitmappack
OK, these look new packages. I'll have a look at 2.0.
-- 
Cheers,
Abou Al Montacir

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20181118/f8e45249/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/20181118/f8e45249/attachment.sig>