On 20.10.2013 23:59, Ben Hutchings wrote:
On Sun, 2013-10-20 at 23:44 +0200, Matthias Klose wrote:
Am 20.10.2013 22:58, schrieb Ben Hutchings:
On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote:
Am 20.10.2013 00:25, schrieb Ben Hutchings:
On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose
On Sun, 2013-10-20 at 23:44 +0200, Matthias Klose wrote:
> Am 20.10.2013 22:58, schrieb Ben Hutchings:
> > On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote:
> >> Am 20.10.2013 00:25, schrieb Ben Hutchings:
> >>> On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote:
> Control: severit
Am 20.10.2013 22:58, schrieb Ben Hutchings:
> On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote:
>> Am 20.10.2013 00:25, schrieb Ben Hutchings:
>>> On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote:
Control: severity -1 important Control: tags -1 + moreinfo
>> In file inc
On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote:
> Am 20.10.2013 00:25, schrieb Ben Hutchings:
> > On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote:
> >> Control: severity -1 important Control: tags -1 + moreinfo
> >>
> In file included from :0:0:
> /usr/include/stdc-pred
Am 20.10.2013 00:25, schrieb Ben Hutchings:
> On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote:
>> Control: severity -1 important Control: tags -1 + moreinfo
>>
In file included from :0:0:
/usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No
such file
>>> or dir
On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote:
> Control: severity -1 important
> Control: tags -1 + moreinfo
>
> > > In file included from :0:0:
> > > /usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No such
> > > file
> > or directory
> > > #include
> > >
Control: severity -1 important
Control: tags -1 + moreinfo
> > In file included from :0:0:
> > /usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No such file
> or directory
> > #include
> > ^
> compilation terminated.
>
> It looks like I can avoid this by c
Control: found -1 4.8.2-1
Control: tag -1 - moreinfo
Control: affects -1 src:linux
Control: severity -1 grave
This also affects linux-image-3.11-trunk-amd64:i386, and presumably
linux-image-3.11-1-amd64:i386, and might also affect
linux-image-3.11-1-powerpc64:powerpc (at least the warnings appear
On 21.08.2013 13:07, Matthias Klose wrote:
Control: tags -1 + moreinfo
Am 26.07.2013 17:53, schrieb Zlatko Calusic:
Actually, I now see that when gcc-4.8 is downgraded to 4.8.1-2, the gcc package
gets downgraded to 4.7.2-1. So probaby all gcc-4.8 version have the problem.
Last i386 gcc version
Control: tags -1 + moreinfo
Am 26.07.2013 17:53, schrieb Zlatko Calusic:
> Actually, I now see that when gcc-4.8 is downgraded to 4.8.1-2, the gcc
> package
> gets downgraded to 4.7.2-1. So probaby all gcc-4.8 version have the problem.
> Last i386 gcc version that successfully compiles 64bit kern
Actually, I now see that when gcc-4.8 is downgraded to 4.8.1-2, the gcc
package gets downgraded to 4.7.2-1. So probaby all gcc-4.8 version have
the problem. Last i386 gcc version that successfully compiles 64bit
kernel is: gcc version 4.7.3 (Debian 4.7.3-5)
--
Zlatko
--
To UNSUBSCRIBE, email
Package: gcc-4.8
Version: 4.8.1-7
Severity: normal
Somewhere after 4.8.1-2 (I believe that version worked OK) I lost the
ability to compile a working 64bit kernel on a 32bit userspace
machine. This report is sent from a full 64bit machine, but it
pertains only to the 32bit version of gcc-4.8 (same
12 matches
Mail list logo
