On 14 February 2016 at 17:52, Nicolas Pitre wrote:
> On Sun, 14 Feb 2016, Ard Biesheuvel wrote:
>
>> On 13 February 2016 at 22:57, Nicolas Pitre wrote:
>> > On Sat, 13 Feb 2016, Ard Biesheuvel wrote:
>> >
>> >> On 12 February 2016 at 22:01, Arnd Bergmann wrote:
>> >> > However, I did stumble ove
On Sun, 14 Feb 2016, Ard Biesheuvel wrote:
> On 13 February 2016 at 22:57, Nicolas Pitre wrote:
> > On Sat, 13 Feb 2016, Ard Biesheuvel wrote:
> >
> >> On 12 February 2016 at 22:01, Arnd Bergmann wrote:
> >> > However, I did stumble over an older patch I did now, which I could
> >> > not remembe
On 13 February 2016 at 22:57, Nicolas Pitre wrote:
> On Sat, 13 Feb 2016, Ard Biesheuvel wrote:
>
>> On 12 February 2016 at 22:01, Arnd Bergmann wrote:
>> > However, I did stumble over an older patch I did now, which I could
>> > not remember what it was good for. It does fix the problem, and
>>
On Sat, 13 Feb 2016, Ard Biesheuvel wrote:
> On 12 February 2016 at 22:01, Arnd Bergmann wrote:
> > However, I did stumble over an older patch I did now, which I could
> > not remember what it was good for. It does fix the problem, and
> > it seems to be a better solution.
> >
> > Arnd
>
On 12 February 2016 at 22:01, Arnd Bergmann wrote:
> On Friday 12 February 2016 13:21:33 Nicolas Pitre wrote:
>> On Fri, 12 Feb 2016, Arnd Bergmann wrote:
>>
>> > On Friday 12 February 2016 14:32:20 Mauro Carvalho Chehab wrote:
>> > > Em Fri, 12 Feb 2016 15:27:18 +0100
>> > > Arnd Bergmann escrev
On Friday 12 February 2016 16:38:53 Nicolas Pitre wrote:
> On Fri, 12 Feb 2016, Arnd Bergmann wrote:
>
> > On Friday 12 February 2016 13:21:33 Nicolas Pitre wrote:
> > > This is all related to the gcc bug for which I produced a test case
> > > here:
> > >
> > > http://article.gmane.org/gmane.lin
On Fri, 12 Feb 2016, Arnd Bergmann wrote:
> On Friday 12 February 2016 13:21:33 Nicolas Pitre wrote:
> > This is all related to the gcc bug for which I produced a test case
> > here:
> >
> > http://article.gmane.org/gmane.linux.kernel.cross-arch/29801
> >
> > Do you know if this is fixed in rec
On Friday 12 February 2016 13:21:33 Nicolas Pitre wrote:
> On Fri, 12 Feb 2016, Arnd Bergmann wrote:
>
> > On Friday 12 February 2016 14:32:20 Mauro Carvalho Chehab wrote:
> > > Em Fri, 12 Feb 2016 15:27:18 +0100
> > > Arnd Bergmann escreveu:
> > >
> > > > I noticed a build error in some randcon
On Fri, 12 Feb 2016, Arnd Bergmann wrote:
> On Friday 12 February 2016 14:32:20 Mauro Carvalho Chehab wrote:
> > Em Fri, 12 Feb 2016 15:27:18 +0100
> > Arnd Bergmann escreveu:
> >
> > > I noticed a build error in some randconfig builds in the zl10353 driver:
> > >
> > > dvb-frontends/zl10353.c:
On Friday 12 February 2016 14:32:20 Mauro Carvalho Chehab wrote:
> Em Fri, 12 Feb 2016 15:27:18 +0100
> Arnd Bergmann escreveu:
>
> > I noticed a build error in some randconfig builds in the zl10353 driver:
> >
> > dvb-frontends/zl10353.c:138: undefined reference to `ilog2_NaN'
> > dvb-front
Em Fri, 12 Feb 2016 15:27:18 +0100
Arnd Bergmann escreveu:
> I noticed a build error in some randconfig builds in the zl10353 driver:
>
> dvb-frontends/zl10353.c:138: undefined reference to `ilog2_NaN'
> dvb-frontends/zl10353.c:138: undefined reference to `__aeabi_uldivmod'
>
> The problem
I noticed a build error in some randconfig builds in the zl10353 driver:
dvb-frontends/zl10353.c:138: undefined reference to `ilog2_NaN'
dvb-frontends/zl10353.c:138: undefined reference to `__aeabi_uldivmod'
The problem can be tracked down to the use of -fprofile-arcs (using
CONFIG_GCOV_PROFI
12 matches
Mail list logo
