[Pkg-pascal-devel] Build failures on mipsel

[Abou Al Montacir]

Hi Peter,

Sorry for my late answer.

On Sat, 2023-03-04 at 14:41 +0000, Peter B wrote:
> I guess /etc/fpc.cfg comes from fpcmkcfg
Yes during post install. See [1] and [2].
> 
> Is it worth considering adding a run of fpcmkcfg to the end of the builds?
No, it should be created upon installation
> 
> The output would then appear in the log and would
> allow problems like this to be investigated without needing a porter box.
We depend on the gcc that is installed in the end system and not in the build
one.
So this will not help.
See [3] for more information.
> 
> Is there any other way I can see an /etc/fpc.cfg on mipsel?
Yes, try to figure out why the post installation script does not go to the right
line [1].

[1]: https://salsa.debian.org/pascal-team/fpc/-/blob/master/debian/fp-compiler.postinst.in#L28-29
[2]: https://salsa.debian.org/pascal-team/fpc/-/blob/master/debian/fp-compiler.postinst.in#L30-32

[3]: https://salsa.debian.org/pascal-team/fpc/-/blob/master/debian/fp-compiler.triggers.in#L1

-- 
Cheers,
Abou Al Montacir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20230307/2480abd3/attachment.htm>
-------------- 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/20230307/2480abd3/attachment.sig>