Hi Paul,
On Sun, 2022-01-02 at 08:19 +0100, Paul Gevers wrote:
> Hi,
>
> On 29-12-2021 23:47, Abou Al Montacir wrote:
> > So it should work correctly on all targets.
>
> Does this work correctly on all multiarch architectures too? I inspected
> only my own installation and there it only has cpui386 and cpux86_64.
If you check on a porter box for ARM or power PC, you will find only arm or ppc
related ifdefs.
So it works for all architectures, but not multiarch.
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.
>
> > However, it is true that if a new gcc version is installed after FPC
> > then the logic will fall down.
>
> Can't we use a wildcard for the version number? I mean, after 11 comes
> 12 and 13 and ...
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*/*
>
> > If this is judged OK, I propose to close this ticket
>
> As long as we have a new fpc in every Debian release, we're fine in
> Debian, but e.g. Ubuntu users may experience issues when they carry the
> same fpc over to a new version of Ubuntu that comes with a new gcc
> version. So I don't think it's nice.
If we can add a trigger then we can run dpkg-reconfigure fp-compiler-${VERSION}
and get it updated.
--
Cheers,
Abou Al Montacir
signature.asc
Description: This is a digitally signed message part
