On Tue, Jun 18, 2013 at 8:02 PM, John David Anglin wrote:
> Hi Aurelien,
>
>
> On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote:
>
>> This is true that they have recently contacted me through another email
>> address, but I haven't found time to work on that. Just stay tuned.
>
>
> That's great news
On 14-06-13 21:11, Thorsten Glaser wrote:
> Wouter, Mikael: input on switching C/C++ to 4.8?
We don't have much data either way, do we?
I suppose it shouldn't be too much of a problem, but I can't be sure. In
the past we've usually taken the plunge, and filed bugs if things go
really bad.
--
Th
Hi Aurelien,
On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote:
This is true that they have recently contacted me through another
email
address, but I haven't found time to work on that. Just stay tuned.
That's great news.
Helge and I have been working away as best we can to maintain the
po
On Fri, Jun 14, 2013 at 01:12:30PM +0200, Matthias Klose wrote:
> Am 13.06.2013 16:46, 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 Debia
Am 15.06.2013 03:22, schrieb Stephan Schreiber:
> GCC-4.8 should become the default on ia64 soon; some other changes are
> desirable:
> - The transition of gcc-4.8/libgcc1 to libunwind8.
> - A removal of the libunwind7 dependency of around 4600 packages on ia64 -
> when
> they are updated next ti
GCC-4.8 should become the default on ia64 soon; some other changes are
desirable:
- The transition of gcc-4.8/libgcc1 to libunwind8.
- A removal of the libunwind7 dependency of around 4600 packages on
ia64 - when they are updated next time after the transition. The
libc6.1 should (likely) de
Matthias Klose dixit:
>> I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
>> until the 4.8 one stops FTBFSing.
>
>please send a patch.
For gcc-defaults? I think that one is trivial…
For gcj? I did not take Compiler Design in what two semesters
of Uni I managed until I ran out of mone
Am 13.06.2013 16:46, 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 from other port maintaine
Am 13.06.2013 21:47, schrieb Thorsten Glaser:
> 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
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
15 matches
Mail list logo