On Tue, 13 Jun 2017 20:41:25 +0300
Adrian Bunk wrote:
> On Tue, Jun 13, 2017 at 11:57:55AM -0400, Celejar wrote:
> > On Mon, 12 Jun 2017 10:45:17 +0300
> > Adrian Bunk wrote:
> >
> > > On Fri, Jun 09, 2017 at 07:58:12AM -0400, Celejar wrote:
> > > > Hi,
...
> > > > line "root_cmd = fakeroot")
On Tue, Jun 13, 2017 at 11:57:55AM -0400, Celejar wrote:
> On Mon, 12 Jun 2017 10:45:17 +0300
> Adrian Bunk wrote:
>
> > On Fri, Jun 09, 2017 at 07:58:12AM -0400, Celejar wrote:
> > > Hi,
> > >
> > > I've been building kernels (vanilla from upstream) for years with
> > > kernel-package (typical
On Mon, 12 Jun 2017 10:45:17 +0300
Adrian Bunk wrote:
> On Fri, Jun 09, 2017 at 07:58:12AM -0400, Celejar wrote:
> > Hi,
> >
> > I've been building kernels (vanilla from upstream) for years with
> > kernel-package (typical command line: "time make-kpkg -j2 --initrd
> > --revision 1.custom kernel
On Fri, Jun 09, 2017 at 07:58:12AM -0400, Celejar wrote:
> Hi,
>
> I've been building kernels (vanilla from upstream) for years with
> kernel-package (typical command line: "time make-kpkg -j2 --initrd
> --revision 1.custom kernel_image"; .kernel-pkg.conf contains just the
> line "root_cmd = faker
On Sun, 11 Jun 2017 14:52:55 +0200
deloptes wrote:
> Celejar wrote:
>
> > So I'll have to decide whether to report against kernel-package, gcc,
> > or not at all.
>
> build a simple and clean chroot and test there. If bug present report if not
> use the kernel build there on your current system
Celejar wrote:
> So I'll have to decide whether to report against kernel-package, gcc,
> or not at all.
build a simple and clean chroot and test there. If bug present report if not
use the kernel build there on your current system.
Avoid mixing build and production systems if possible - chroot i
On Sat, Jun 10, 2017 at 10:51 PM, Celejar wrote:
> On Sat, 10 Jun 2017 09:37:39 -0400
> kamaraju kusumanchi wrote:
>
>> On Fri, Jun 9, 2017 at 7:58 AM, Celejar wrote:
>> > Any ideas? Is this a bug I should be filing against kernel-package (or
>> > anywhere else)?
>>
>> Two things
>>
>> 1) Does t
On Sat, 10 Jun 2017 09:37:39 -0400
kamaraju kusumanchi wrote:
> On Fri, Jun 9, 2017 at 7:58 AM, Celejar wrote:
> > Any ideas? Is this a bug I should be filing against kernel-package (or
> > anywhere else)?
>
> Two things
>
> 1) Does the problem go away if you upgrade to the latest compiler?
>
On Fri, Jun 9, 2017 at 7:58 AM, Celejar wrote:
> Any ideas? Is this a bug I should be filing against kernel-package (or
> anywhere else)?
Two things
1) Does the problem go away if you upgrade to the latest compiler?
Based on the error message, I believe you are using gcc 4.9? But it is
not clear
Hi,
I've been building kernels (vanilla from upstream) for years with
kernel-package (typical command line: "time make-kpkg -j2 --initrd
--revision 1.custom kernel_image"; .kernel-pkg.conf contains just the
line "root_cmd = fakeroot") without problem. Recently, the builds have
begun to fail with m
10 matches
Mail list logo