Re: proof for hardware damage on (at least) elgar

2014-01-10 Thread John Paul Adrian Glaubitz
On 01/10/2014 12:23 AM, Thorsten Glaser wrote: > make[2]: *** No rule to make target > `/usr/ynclude/m68k-linux-gnu/bits/stdio_lim.h', needed by `vendor.lo'. Stop. This build was on September, 16 2013, one month before I bought new FPM memory modules and replaced all memory in elgar. The modules

Re: proof for hardware damage on (at least) elgar

2014-01-10 Thread Geert Uytterhoeven
On Fri, Jan 10, 2014 at 12:51 AM, John Paul Adrian Glaubitz wrote: >> make[2]: *** No rule to make target >> `/usr/ynclude/m68k-linux-gnu/bits/stdio_lim.h', needed by `vendor.lo'. Stop. >> >> 69h = 0110 1001 == i >> 79h = 0111 1001 == y >> Δ = 0001 > > Jeez, that took me several minutes o

Re: proof for hardware damage on (at least) elgar

2014-01-09 Thread John Paul Adrian Glaubitz
On 01/10/2014 12:23 AM, Thorsten Glaser wrote: > make[2]: *** No rule to make target > `/usr/ynclude/m68k-linux-gnu/bits/stdio_lim.h', needed by `vendor.lo'. Stop. > > 69h = 0110 1001 == i > 79h = 0111 1001 == y > Δ = 0001 Jeez, that took me several minutes of staring at the screen until

Re: proof for hardware damage on (at least) elgar

2014-01-09 Thread John Paul Adrian Glaubitz
On 01/10/2014 12:23 AM, Thorsten Glaser wrote: > tg@blau:~ $ hd << 69 0A - |i.| > tg@blau:~ $ hd << 79 0A - |y.| > > 69h = 0110 1001 > 79h = 0111 1001 > Δ = 0001 I have no idea what yo

proof for hardware damage on (at least) elgar

2014-01-09 Thread Thorsten Glaser
[24]m68k 3:5.0.1+dfsg1-1 [25]Build-Attempted 115d 14h 28m [26]elgar out-of-date net:source [27]old | [28]all (2) Tail of log for [51]ntop on [52]m68k: Making check in . make[2]: Entering directory `/«BUILDDIR»/ntop-5.0.1+dfsg1' CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh ./missing --run