Nicolas Boulenguez writes:
> Ludovic, could you describe the scenario you are trying to prevent?
The scenario I'd like to prevent is wherein most architectures use
gnat-4.9 to build all other Ada packages but one architecture decides to
use gnat-4.8 instead, resulting in compilation problems and w
Thorsten Glaser writes:
> Right, but there is still the transition period to take care of.
There are two transition periods. The first one started on 2014-02-03
with the announcement of gnat-4.9 and ended on 2014-05-01 with the
upload of gnat (=4.9). This three-month period was to bootstrap and
Ludovic Brenta dixit:
>It is our policy[1] to support the same version of gnat on all
>architectures. The package gnat exists for this very purpose. Allowing
Right, but there is still the transition period to take care of.
>gnat to depend on different versions of gnat-x.y on different
>archite
It is our policy[1] to support the same version of gnat on all
architectures. The package gnat exists for this very purpose. Allowing
gnat to depend on different versions of gnat-x.y on different
architectures would defeat this purpose. If some architecture cannot
support the chosen version of g
Matthias Klose dixit:
>sure, the immediate problem is solved until the next port with a version
>discrepancy.
Well there is one… m68k has gnat-4.6 (although Andreas Schwab did
post experimental patches for 4.9 today or yesterday, IIRC).
So this change broke it for m68k and, what’s worse, made it
5 matches
Mail list logo
