Steven Chamberlain dixit:
>Before that can be changed, I think the gcc-defaults package expects
>package version (>= 4.8.1-2) whereas m68k still has only the 4.8.0-7 you
>uploaded.
Right. That’s because gcj FTBFSes.
>You will also first need newer binutils (>= 2.23.52) which is still in
>the bui
Hi,
On 13/06/13 20:47, Thorsten Glaser wrote:
> From me nothing against switching C/C++ to 4.8 for m68k at
> this point, but I’d like to hear at least Wouter’s opinion
> on that, and possibly Mikael [...]
Before that can be changed, I think the gcc-defaults package expects
package version (>= 4.8
Matthias Klose dixit:
>The Java and D frontends now default to 4.8 on all architectures, the Go
>frontend stays at 4.7 until 4.8 get the complete Go 1.1 support.
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.
From me nothing against switching C/C++
Am Donnerstag, den 13.06.2013, 15:46 +0100 schrieb Steven Chamberlain:
> Hi,
>
> On 13/06/13 13:51, Matthias Klose wrote:
> > GCC 4.8 is now the default on all x86 architectures, and on all ARM
> > architectures (the latter confirmed by the Debian ARM porters). I did not
> > get
> > any feedback
Hi,
On 13/06/13 13:51, Matthias Klose wrote:
> GCC 4.8 is now the default on all x86 architectures, and on all ARM
> architectures (the latter confirmed by the Debian ARM porters). I did not get
> any feedback from other port maintainers, so unless this does change and port
> maintainers get invo
Am 07.05.2013 15:25, schrieb Matthias Klose:
> The decision when to make GCC 4.8 the default for other architectures is
> left to the Debian port maintainers.
[...]
> Information on porting to GCC 4.8 from previous versions of GCC can be
> found in the porting guide http://gcc.gnu.org/gcc-4.8/port
6 matches
Mail list logo
