On Fri, Oct 12, 2018 at 12:33 AM Borislav Petkov wrote:
>
> On Fri, Oct 12, 2018 at 12:08:07AM +0900, Masahiro Yamada wrote:
> > Install lz4c, and run 'make' again.
> > Almost all objects have been built there,
> > so you will finish it soon.
>
> So when this LZ4 thing got added at the time, the
On Fri, Oct 12, 2018 at 12:33 AM Borislav Petkov wrote:
>
> On Fri, Oct 12, 2018 at 12:08:07AM +0900, Masahiro Yamada wrote:
> > Install lz4c, and run 'make' again.
> > Almost all objects have been built there,
> > so you will finish it soon.
>
> So when this LZ4 thing got added at the time, the
Hi Borislav,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc7 next-20181011]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Borislav,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc7 next-20181011]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Fri, Oct 12, 2018 at 12:08:07AM +0900, Masahiro Yamada wrote:
> Install lz4c, and run 'make' again.
> Almost all objects have been built there,
> so you will finish it soon.
So when this LZ4 thing got added at the time, the lz4 package had to be
downloaded and built and installed and it wasn't
On Fri, Oct 12, 2018 at 12:08:07AM +0900, Masahiro Yamada wrote:
> Install lz4c, and run 'make' again.
> Almost all objects have been built there,
> so you will finish it soon.
So when this LZ4 thing got added at the time, the lz4 package had to be
downloaded and built and installed and it wasn't
On Thu, Oct 11, 2018 at 5:54 PM Borislav Petkov wrote:
>
> On Thu, Oct 11, 2018 at 01:26:23PM +0900, Masahiro Yamada wrote:
> > So, the cause of the failure is clear enough
> > from the build log.
>
> Sure but it wasts unnecessary build cycles and appears only after all
> the compilation units
On Thu, Oct 11, 2018 at 5:54 PM Borislav Petkov wrote:
>
> On Thu, Oct 11, 2018 at 01:26:23PM +0900, Masahiro Yamada wrote:
> > So, the cause of the failure is clear enough
> > from the build log.
>
> Sure but it wasts unnecessary build cycles and appears only after all
> the compilation units
On Thu, Oct 11, 2018 at 01:26:23PM +0900, Masahiro Yamada wrote:
> So, the cause of the failure is clear enough
> from the build log.
Sure but it wasts unnecessary build cycles and appears only after all
the compilation units have been produced.
> It is weird to check only lz4c.
> If
On Thu, Oct 11, 2018 at 01:26:23PM +0900, Masahiro Yamada wrote:
> So, the cause of the failure is clear enough
> from the build log.
Sure but it wasts unnecessary build cycles and appears only after all
the compilation units have been produced.
> It is weird to check only lz4c.
> If
Hi Borislav,
On Thu, Oct 11, 2018 at 7:23 AM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> When building randconfigs, the build fails at kernel compression stage
> due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
> by randconfig. The result looks somethins like
Hi Borislav,
On Thu, Oct 11, 2018 at 7:23 AM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> When building randconfigs, the build fails at kernel compression stage
> due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
> by randconfig. The result looks somethins like
On 10/10/18 3:23 PM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> When building randconfigs, the build fails at kernel compression stage
> due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
> by randconfig. The result looks somethins like this:
>
> (cat
On 10/10/18 3:23 PM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> When building randconfigs, the build fails at kernel compression stage
> due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
> by randconfig. The result looks somethins like this:
>
> (cat
From: Borislav Petkov
When building randconfigs, the build fails at kernel compression stage
due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
by randconfig. The result looks somethins like this:
(cat arch/x86/boot/compressed/vmlinux.bin
From: Borislav Petkov
When building randconfigs, the build fails at kernel compression stage
due to missing lz4 on the system but CONFIG_KERNEL_LZ4 has been selected
by randconfig. The result looks somethins like this:
(cat arch/x86/boot/compressed/vmlinux.bin
16 matches
Mail list logo