similar to: Processed (with 1 error): block 827061 with 828253 828367 828586 828309 828307 828513 812166 828412 828298 828277

Package: xen Version: 4.6.0-1 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in

Debian bug 812166[0] reported this build failure due to Wmisleading-indentation with gcc-6: non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] switch (c->x86_vendor) { ^~~~~~ non-fatal.c:97:5: note: ...this 'if' clause, but it is not if (

On Wed, 2016-01-20 at 20:16 -0800, Martin Michlmayr wrote: > Package: xen > Version: 4.6.0-1 > Severity: important > User: debian-gcc at lists.debian.org > Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation > > This package fails to build with GCC 6.??GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. >

On 22/01/16 14:38, Ian Campbell wrote: > Debian bug 812166[0] reported this build failure due to > Wmisleading-indentation with gcc-6: > > non-fatal.c: In function 'init_nonfatal_mce_checker': > non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] > switch (c->x86_vendor) { > ^~~~~~ > >

Originally posted on github, reported to the right place. I would like to open a discussion about how `to_json` and `as_json` operates in Rails from a performance standpoint. I''m using Rails 3.2 but this issue applies to almost all versions of Rails. Our use case presents the challenge in sending out potentially large JSON (or XML, but we''ll focus on JSON rendering here)

Is it possible to create a Startup Item for WEBrick? My startup item, named swu, works fine when I run it from the command line, just not when the computer is starting up. I''m wondering if some resources are missing for ruby to load at this point... or something. Here''s output from /var/log/system.log... Any suggestions would be appreciated. Aug 18 21:18:58 localhost