On Mon, June 22, 2015 12:18:27 David Faure wrote:
> On Sunday 21 June 2015 15:04:58 Michael Pyne wrote:
> > On Fri, June 19, 2015 20:40:39 Rohan Garg wrote:
> > > Hi
> > > I'm trying to compile kcoreaddons on ARM with clang and I'm hitting
> > > this build failiure :
> > >
> > > 06:22:27 ../../../
2015-06-22 13:18 GMT+03:00 David Faure :
> I don't follow. How does 0x858458F6 not fit into an int, even on a 32 bit
> machine?
> OK, this is just about signed/unsigned, not about really wider.
> So yeah the bug is that glibc should use unsigned int there instead,
> but the issue you mention "the c
On Sunday 21 June 2015 15:04:58 Michael Pyne wrote:
> On Fri, June 19, 2015 20:40:39 Rohan Garg wrote:
> > Hi
> > I'm trying to compile kcoreaddons on ARM with clang and I'm hitting
> > this build failiure :
> >
> > 06:22:27 ../../../src/lib/io/kfilesystemtype.cpp:112:10: error: case
> > value eva
On Fri, June 19, 2015 20:40:39 Rohan Garg wrote:
> Hi
> I'm trying to compile kcoreaddons on ARM with clang and I'm hitting
> this build failiure :
>
> 06:22:27 ../../../src/lib/io/kfilesystemtype.cpp:112:10: error: case
> value evaluates to 2240043254, which cannot be narrowed to type
> '__fsword
Hi
I'm trying to compile kcoreaddons on ARM with clang and I'm hitting
this build failiure :
06:22:27 ../../../src/lib/io/kfilesystemtype.cpp:112:10: error: case
value evaluates to 2240043254, which cannot be narrowed to type
'__fsword_t' (aka 'int') [-Wc++11-narrowing]
06:22:27 case RAMFS_MAG