On Fri 2018-04-20 15:30:03, Daniel Micay wrote:
> Well, that's not related, it's just this:
>
> #ifdef __GNUC__
> #if (__GNUC__ == 3 && __GNUC_MINOR__ < 3)
> #error Your compiler is too buggy; it is known to miscompile kernels.
> #errorKnown good compilers: 3.3, 4.x
> #endif
> #if GCC_VERSION
Well, that's not related, it's just this:
#ifdef __GNUC__
#if (__GNUC__ == 3 && __GNUC_MINOR__ < 3)
#error Your compiler is too buggy; it is known to miscompile kernels.
#errorKnown good compilers: 3.3, 4.x
#endif
#if GCC_VERSION >= 40800 && GCC_VERSION < 40803
#error Your compiler is too bugg
On Fri 2018-04-20 15:18:32, Daniel Micay wrote:
> On 20 April 2018 at 15:15, Pavel Machek wrote:
> > Hi!
> >
> >> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
> >> >> a particular subset of arm architectures? (My local builds of arm all
> >> >> succeed, for example. Can
On 20 April 2018 at 15:15, Pavel Machek wrote:
> Hi!
>
>> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
>> >> a particular subset of arm architectures? (My local builds of arm all
>> >> succeed, for example. Can you send your failing config?) I'll take a
>> >> closer loo
Hi!
> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
> >> a particular subset of arm architectures? (My local builds of arm all
> >> succeed, for example. Can you send your failing config?) I'll take a
> >> closer look on Monday if Daniel doesn't beat me to it.
> >
> > Da
On Fri, Apr 20, 2018 at 08:05:17AM -0700, Kees Cook wrote:
> On Fri, Apr 20, 2018 at 12:34 AM, Pavel Machek wrote:
> > On Sun 2018-04-15 11:00:06, Kees Cook wrote:
> >> On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek wrote:
> >> > Hi!
> >> >
> >> >> Thanks.
> >> >>
> >> >> Ok, let me try to bisect
On Fri, Apr 20, 2018 at 12:34 AM, Pavel Machek wrote:
> On Sun 2018-04-15 11:00:06, Kees Cook wrote:
>> On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek wrote:
>> > Hi!
>> >
>> >> Thanks.
>> >>
>> >> Ok, let me try to bisect it. Compile-problem should be easy...
>> >>
>> >> Hmm. And as it is compil
On Sun 2018-04-15 11:00:06, Kees Cook wrote:
> On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek wrote:
> > Hi!
> >
> >> Thanks.
> >>
> >> Ok, let me try to bisect it. Compile-problem should be easy...
> >>
> >> Hmm. And as it is compile-problem in single file, it should even be
> >> reasonably fast.
On Sun 2018-04-15 11:00:06, Kees Cook wrote:
> On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek wrote:
> > Hi!
> >
> >> Thanks.
> >>
> >> Ok, let me try to bisect it. Compile-problem should be easy...
> >>
> >> Hmm. And as it is compile-problem in single file, it should even be
> >> reasonably fast.
On Sun, Apr 15, 2018 at 10:39 AM, Pavel Machek wrote:
> Hi!
>
>> Thanks.
>>
>> Ok, let me try to bisect it. Compile-problem should be easy...
>>
>> Hmm. And as it is compile-problem in single file, it should even be
>> reasonably fast. I did not realize how easy it would be:
>>
>> #!/bin/bash
>> s
Hi!
> Thanks.
>
> Ok, let me try to bisect it. Compile-problem should be easy...
>
> Hmm. And as it is compile-problem in single file, it should even be
> reasonably fast. I did not realize how easy it would be:
>
> #!/bin/bash
> set -e
> cp config.ok .config
> yes '' | ARCH=arm make lib/string
On Wed 2018-04-04 12:59:51, Tony Lindgren wrote:
> * Pavel Machek [180404 18:47]:
> > Hi!
> >
> > > > When trying to build kernel for N900, I get:
> > > >
> > > > CC lib/timerqueue.o
> > > > CC lib/vsprintf.o
> > > > lib/string.c: In function 'strstr':
> > > > lib/string.
* Pavel Machek [180404 18:47]:
> Hi!
>
> > > When trying to build kernel for N900, I get:
> > >
> > > CC lib/timerqueue.o
> > > CC lib/vsprintf.o
> > > lib/string.c: In function 'strstr':
> > > lib/string.c:478:8: error: inlining failed in call to
> > > always_inline
Hi!
> > When trying to build kernel for N900, I get:
> >
> > CC lib/timerqueue.o
> > CC lib/vsprintf.o
> > lib/string.c: In function 'strstr':
> > lib/string.c:478:8: error: inlining failed in call to
> > always_inline 'strlen': function not inlinable
> > lib/strin
Hi!
> > > Please do not add any v4.18 destined stuff to your linux-next included
> > > trees until after v4.17-rc1 has been released.
> > >
> > > Changes since 20180403:
> > >
> > > The vfs tree still had its build failure for which I reverted a commit.
> > >
> > > Non-merge commits (relative t
* Pavel Machek [180404 07:50]:
> Hi!
>
> > Please do not add any v4.18 destined stuff to your linux-next included
> > trees until after v4.17-rc1 has been released.
> >
> > Changes since 20180403:
> >
> > The vfs tree still had its build failure for which I reverted a commit.
> >
> > Non-merge
Hi!
> Please do not add any v4.18 destined stuff to your linux-next included
> trees until after v4.17-rc1 has been released.
>
> Changes since 20180403:
>
> The vfs tree still had its build failure for which I reverted a commit.
>
> Non-merge commits (relative to Linus' tree): 8505
> 8493 fil
17 matches
Mail list logo
