[Pkg-pascal-devel] Bug#892285: /usr/bin/fpcmake: fpcmake should find units in Debian without fiddling with FPCDIR

[Abou Al Montacir]

Hi All,
On Thu, 2018-03-08 at 09:34 +0100, Abou Al Montacir wrote:
> Hi Paul,
> 
> On Thu, 2018-03-08 at 08:44 +0100, Paul Gevers wrote:
> > > Probably none of them need to define FPCDIR.
> > Currently Lazarus FTBFS without it.¹
> I'll have a look at it and try to fix it this WE.
I could finally find time for this issue. There was an issue with fpcmake
looking for fpc executable using a wrong name on amd64 architecture.FPC
executable is ppcx64 while fpcmake was looking for ppcx86_64. I had a commit
fixing this issue: cff270e15f4d9342ea6918a4b69d038df5184af2
However this commit revealed another bug: currently we are shipping
Makefiles.fpc in fpc-source package, which install to /usr/share/fpc-
source/${FPCVER}.However fpcmake seems too look for them at units directories.
This seems more logical and make me remeber the lpk files  for Lazarus.Also by
shipping Makefile.fpc with binaries we get rid of the constraint of depending on
fpc-source to be able to build any fpc programe using fpcmake.
To be discussed more.
-- Cheers,
Abou Al Montacir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20180413/bb569e12/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/20180413/bb569e12/attachment.sig>