On Wed, 2011-03-30 at 11:13 +0200, Samuel Thibault wrote:
> Svante Signell, le Wed 30 Mar 2011 09:18:05 +0200, a écrit :
> > (I don't think the problem is due to qemu-kvm?)
>
> Many problems do come from kvm actually. That's one of the reasons why I
> prefer to use Xen.
>
> > I can of course run the generated makefiles manually, but do not
> > generally know in which order to run them. The most annoying part is
> > that even if the libraries and executables are successfully built by
> > manual intervention, the build-stamp is not created. Does manually
> > creating it make dpkg-buildpackage happy to continue building the
> > package??
I have now tried compiling ghc6_6.10.1+dfsg1-{5,4,3} with
ghc6_6.8.2dfsg1-1.1,6.8.2dfsg1-1+hurd.1, 6.6.1-2 and they all hang at
the same place. I don't think this problem is qemu-related.
Below is the limited information provided by gdb:
gdb ghc6-6.10.1+dfsg1/libraries/cabal-bin
...long configure command there...
[New Thread 15613.5]
[New Thread 15613.6]
Configuring random-1.0.0.1...
^C
Program received signal SIGINT, Interrupt.
0x011120dc in _hurd_intr_rpc_mach_msg () from /lib/libc.so.0.3
(gdb) bt
#0 0x011120dc in _hurd_intr_rpc_mach_msg () from /lib/libc.so.0.3
#1 0x012aa195 in io_read () from /lib/libhurduser.so.0.3
#2 0x01116b61 in ?? () from /lib/libc.so.0.3
#3 0x0111da29 in ?? () from /lib/libc.so.0.3
#4 0x011164ee in ?? () from /lib/libc.so.0.3
#5 0x011d3ce0 in read () from /lib/libc.so.0.3
#6 0x084919c8 in s9qJ_ret ()
#7 0x0861f842 in StgRun ()
#8 0x087c44e0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
How to
