On Tue, Nov 12, 2013 at 11:52 AM, Jakub Jelinek wrote:
> On Tue, Nov 12, 2013 at 11:34:41AM +0400, Kostya Serebryany wrote:
>> On Sun, Nov 10, 2013 at 10:34 PM, FX wrote:
>>
>> > > Unfortunately, we are not able to keep up with the old kernels.
>> > > Two possible ways to go:
>> > > - disable li
On Tue, Nov 12, 2013 at 11:34:41AM +0400, Kostya Serebryany wrote:
> On Sun, Nov 10, 2013 at 10:34 PM, FX wrote:
>
> > > Unfortunately, we are not able to keep up with the old kernels.
> > > Two possible ways to go:
> > > - disable libsanitizer on older kernels
> > > - someone needs to work wit
[text-only]
On Sun, Nov 10, 2013 at 10:34 PM, FX wrote:
>> Unfortunately, we are not able to keep up with the old kernels.
>> Two possible ways to go:
>> - disable libsanitizer on older kernels
>> - someone needs to work with us in upstream repository (llvm) to keep the
>> code old-kernel-comp
> Unfortunately, we are not able to keep up with the old kernels.
> Two possible ways to go:
> - disable libsanitizer on older kernels
> - someone needs to work with us in upstream repository (llvm) to keep the
> code old-kernel-compatible
(It appears to be not only kernel, but binutils.)
I th
[resending text-only]
On Sun, Nov 10, 2013 at 8:51 AM, Konstantin Serebryany
wrote:
> Unfortunately, we are not able to keep up with the old kernels.
> Two possible ways to go:
> - disable libsanitizer on older kernels
> - someone needs to work with us in upstream repository (llvm) to keep th
> In principle, you could try --disable-libsanitizer
> --disable-target-libsanitizer but I am not sure whether that works, a
> fortnight ago, Janne remarked at #gcc that it didn't seem to work – maybe you
> have more luck.
>
> Your Linux 2.6.18 is already quite old (September 2007) thus I would
FX wrote:
I’m building with binutils 2.17.50.0.6, which is a bit old but I cannot find
any mention of needing later binutils on the installation notes.
Is bootstrap broken, or am I missing something?
Second build, this time with trunk binutils. Still fails in libsanitizer at
stage1, this time
> I’m building with binutils 2.17.50.0.6, which is a bit old but I cannot find
> any mention of needing later binutils on the installation notes.
> Is bootstrap broken, or am I missing something?
Second build, this time with trunk binutils. Still fails in libsanitizer at
stage1, this time with:
Trying to build trunk rev. 204619 with --enable-languages=c,c++,fortran on
x86_64-unknown-linux-gnu, I get a build error in stage1-target-libsanitizer:
> ../../../../trunk/libsanitizer/sanitizer_common/sanitizer_linux.cc: Assembler
> messages:
> ../../../../trunk/libsanitizer/sanitizer_common/sa
On Thu, 2008-08-14 at 14:41 -0700, H.J. Lu wrote:
> It should be fixed now.
Thanks a lot for the quick fix.
My problem is that I don't have access to a machine with GFC_REAL_16 and
working autoconf2.59, so possible problems in cut&paste code tend to be
hidden from me.
I'll make special mention
On Thu, Aug 14, 2008 at 1:32 PM, Daniel Berlin <[EMAIL PROTECTED]> wrote:
> Failure:
>
> ../../../libgfortran/intrinsics/cshift0.c: In function 'cshift0':
> ../../../libgfortran/intrinsics/cshift0.c:124: warning: passing
> argument 1 of 'cshift0_i16' from incompatible pointer type
> ../../../libgfo
Failure:
../../../libgfortran/intrinsics/cshift0.c: In function 'cshift0':
../../../libgfortran/intrinsics/cshift0.c:124: warning: passing
argument 1 of 'cshift0_i16' from incompatible pointer type
../../../libgfortran/intrinsics/cshift0.c:236: error: 'GFC_INTGER_16'
undeclared (first use in this
12 matches
Mail list logo
