Hi Michalis, On Thu, 2018-01-18 at 06:43 +0100, Michalis Kamburelis wrote: > The problem is caused by the different directories used by new FPC > 3.0.4 packages (compared to previous versions of FPC in Debian). I must admit that I was expecting many packages to break as the change is too big.But I assume this is worth the pain as now we can install multiple architecture units on the same host. > Doing > > ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4" Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we need to explicitly pass this? > doesn't work, since /usr/lib/fpc/3.0.4 does not exist. This works: > > ./fpmake --globalunitdir="/usr/lib/x86_64-linux-gnu/fpc/3.0.4" I would use DEB_HOST_MULTIARCH=$(dpkg-architecture -qDEB_HOST_MULTIARCH) > To fix this, I suggest to > > - Change / define the $FPCDIR variable inside Debian build scripts, to > point to the new correct directory. I would try to avoid this if possible but indeed seems correct solution > - Or create a symlink /usr/lib/fpc/3.0.4 -> > /usr/lib/x86_64-linux-gnu/fpc/3.0.4 . This brings us back to pre-MA epoch. Let's avoid it. Also not possible in the Debian auto-builder daemon. -- Cheers, Abou Al Montacir
signature.asc
Description: This is a digitally signed message part
