On Thu, 2012-10-25 at 19:47 +0200, Samuel Thibault wrote: > Roland McGrath, le Thu 25 Oct 2012 09:49:51 -0700, a écrit : > > We don't generally handle MIG_BAD_ID. That error indicates a server not > > implementing the protocol for which it's being used, which is a server bug. > > Pino, in which case did you actually get MIG_BAD_ID precisely?
See the IRC log from http://www.richtlijn.be/~larstiq/hurd/hurd-2012-08-23 starting with: 14:56:28< braunr> pinotree: i think gnu_srs spotted a conformance problem in glibc It was creating a stack overflow when compiling clisp and using a pipe to create the log file: dpkg-buildpackage -b 2>&1 | tee build.log failed while redirecting with dpkg-buildpackage -b > build.log 2>&1 worked.
