<html><head></head><body><div>Hi Paul,</div><div><br></div><div>On Sun, 2022-01-02 at 08:19 +0100, Paul Gevers wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hi,<br></div><div><br></div><div>On 29-12-2021 23:47, Abou Al Montacir wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>So it should work correctly on all targets.<br></div></blockquote><div><br></div><div>Does this work correctly on all multiarch architectures too? I inspected <br></div><div>only my own installation and there it only has cpui386 and cpux86_64.</div></blockquote><div>If you check on a porter box for ARM or power PC, you will find only arm or ppc related ifdefs.</div><div>So it works for all architectures, but not multiarch.</div><div>If we can safely suppose that all Debian architectures are using the very same GCC version and path, then we can remove the ifdef and have a generic path that works for mutiarch with a minimal effort.</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>However, it is true that if a new gcc version is installed after FPC <br></div><div>then the logic will fall down.<br></div></blockquote><div><br></div><div>Can't we use a wildcard for the version number? I mean, after 11 comes <br></div><div>12 and 13 and ...<br></div></blockquote><div>The wildcards work but only for one directory level. This means /path/to/* and /path/to/prefix* will work, but not /path/to/*/* or /path/to/prefix*/*</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>If this is judged OK, I propose to close this ticket<br></div></blockquote><div><br></div><div>As long as we have a new fpc in every Debian release, we're fine in <br></div><div>Debian, but e.g. Ubuntu users may experience issues when they carry the <br></div><div>same fpc over to a new version of Ubuntu that comes with a new gcc <br></div><div>version. So I don't think it's nice.</div></blockquote><div>If we can add a trigger then we can run dpkg-reconfigure fp-compiler-${VERSION} and get it updated.</div><div style="caret-color: rgb(46, 52, 54); color: rgb(46, 52, 54); font-family: Cantarell; font-size: 14.666666984558105px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;"><span><pre>-- <br></pre><pre>Cheers,
Abou Al Montacir
</pre></span></div><br class="Apple-interchange-newline"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"></blockquote></body></html>