[Pkg-pascal-devel] problems with compiling astap

[Abou Al Montacir]

Hi Thorsten,

Sorry it seems I forgot to copy you in my last message.

On Sat, 2022-03-05 at 12:19 +0100, Abou Al Montacir wrote:
> Hi Thosten,
> 
> On Sat, 2022-03-05 at 09:01 +0000, Thorsten Alteholz wrote:
> Hi,
> 
> there is a problem compiling a new upstream version of astap using 
> lazbuild from the new version 2.2.0 of lcl-utils. 
> Can you please have a look at [1]. It contains some errors that I don't 
> know how to resolve:
> 
> 
> lazbuild -B --pcp=/etc/lazarus  astap_linux.lpi
> SetPrimaryConfigPath NewValue="/etc/lazarus" -> "/etc/lazarus"
> Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-iWTOTP"
> Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-va" "compilertest.pas"
> Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-iWTOTP" "-Px86_64" "-Tlinux"
> Hint: (lazarus) [RunTool] "/usr/bin/fpc" "-va" "compilertest.pas" "-Px86_64"
> "-Tlinux"
> Hint: (lazarus) Missing state file of freetypelaz 1.0:
> /usr/lib/lazarus/2.2.0/components/freetype/lib/x86_64-
> linux/freetypelaz.compiled
> Error: (lazarus) unable to create package output directory
> "/usr/lib/lazarus/2.2.0/components/freetype/lib/x86_64-linux" of package
> "freetypelaz 1.0"
> Hint: (lazarus) normal output directory of package freetypelaz 1.0 is not
> writable: "/usr/lib/lazarus/2.2.0/components/freetype/lib/x86_64-linux/"
> TParsedCompilerOptions.SetOutputDirectoryOverride 
> New=/etc/lazarus/lib/freetypelaz/lib/x86_64-linux
> Hint: (lazarus) Missing state file of freetypelaz 1.0:
> /etc/lazarus/lib/freetypelaz/lib/x86_64-linux/freetypelaz.compiled
> Error: (lazarus) unable to create package output directory
> "/etc/lazarus/lib/freetypelaz/lib/x86_64-linux" of package "freetypelaz 1.0"
> Error: (lazarus) [TLazPackageGraph.PreparePackageOutputDirectory] failed to
> create writable directory: /etc/lazarus/lib/freetypelaz/lib/x86_64-linux
> Error: (lazarus) [TLazPackageGraph.CompilePackage] 
> PreparePackageOutputDirectory failed: freetypelaz 1.0
> Error: (lazbuild) Project dependencies of /<<PKGBUILDDIR>>/astap_linux.lpi
> 
> 
> Do you have any idea what went wrong?
> Can you tell why do you set primary configuration files loction to
> /et/lazarus?
> I wouldn't encourage that, because lazarus uses pcp to install lpl files
> (package link files) and /etc/lazarus is not writable for obvious reasons.
I managed to build it using the following patches.

I'm almost sure that -B option is not needed. It will just trigger rebuilding a
bunch of packages, while it is not needed especially if you use gbp with
cowbuilder. I tried it and it builds fine. This will help reducing build time.
You just may want to ensure clean target in debian/rules is correctly working.

Also as said Peter in his mail, you may not want to build depend on Lazarus but
on lcl-utils which provides lazbuild.

Please let me know if you need more help.
-- 
Cheers,
Abou Al Montacir

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20220305/91569ead/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Enable-building-using-GBP.patch
Type: text/x-patch
Size: 727 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20220305/91569ead/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Removed-pcp-from-command-line-options-when-building-.patch
Type: text/x-patch
Size: 599 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20220305/91569ead/attachment-0001.bin>
-------------- 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/20220305/91569ead/attachment.sig>