<html><head></head><body bgcolor="#ffffff" text="#2e3436" link="#2a76c6" vlink="#2e3436"><div>Hi Michalis,</div><div><br></div><div>On Thu, 2018-01-18 at 06:43 +0100, Michalis Kamburelis wrote:</div><blockquote type="cite"><pre>The problem is caused by the different directories used by new FPC
3.0.4 packages (compared to previous versions of FPC in Debian).
</pre></blockquote><div>I must admit that I was expecting many packages to break as the change is too big.</div><div>But I assume this is worth the pain as now we can install multiple architecture units on the same host.</div><blockquote type="cite"><pre>
Doing
./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
</pre></blockquote><div>Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we need to explicitly pass this?</div><blockquote type="cite"><pre>
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"
</pre></blockquote><div>I would use </div><pre>DEB_HOST_MULTIARCH=$(dpkg-architecture -qDEB_HOST_MULTIARCH)</pre><blockquote type="cite"><pre>
To fix this, I suggest to
- Change / define the $FPCDIR variable inside Debian build scripts, to
point to the new correct directory.
</pre></blockquote><div>I would try to avoid this if possible but indeed seems correct solution</div><blockquote type="cite"><pre>
- Or create a symlink /usr/lib/fpc/3.0.4 ->
/usr/lib/x86_64-linux-gnu/fpc/3.0.4 .
</pre></blockquote><div>This brings us back to pre-MA epoch. Let's avoid it. Also not possible in the Debian auto-builder daemon.</div><div><div style="white-space: normal;"><span><pre><pre>-- <br></pre>Cheers,
Abou Al Montacir</pre></span></div></div></body></html>