[Pkg-pascal-devel] compiling packages as user (and autopkgtest)
Paul Gevers
elbrus at debian.org
Sat Nov 17 20:18:23 GMT 2018
Hi Abou
On 17-11-18 08:47, Abou Al Montacir wrote:
> The following files failed unexpectedly:
>
> /usr/lib/lazarus/default/components/tachart/tachartwmf.lpk
>
> /usr/lib/lazarus/default/components/turbopower_ipro/design/turbopoweriprodsgn.lpk
>
>
> There are only 2 unexpected failures.
<snip>
> This package looks for Windows unit, I don't think it will compile under
> Linux.
I have compiled the list on my machine. So they pass for me (I run
buster with all the lazarus packages from experimental installed).
> The second one compiled correctly manually. So I suppose it was
> depending on a package that was compiler after it in the list.
So you agree with me that this seems to depend on the order that we
compile the packages? If that is the case, how do we automatically
define the right order?
> I think the man pages are legacy. Use lazbuild -h for that.
Than we should generate the man page from lazbuild -h. There is the
help2man helper function to do that.
>> 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.
So do I need to add each package that I compile to be available for the
others? Why not add them by default?
Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20181117/80cabcb6/attachment.sig>
More information about the Pkg-pascal-devel
mailing list