GaloisInc / HaLVM

The Haskell Lightweight Virtual Machine (HaLVM): GHC running on Xen
BSD 3-Clause "New" or "Revised" License
1.05k stars 88 forks source link

Looking for some guidance on Fedora packages #8

Closed johnpmayer closed 11 years ago

johnpmayer commented 11 years ago

I'm having trouble fulfilling the errors from configure

WARNING: Couldn't find required program xm (needed to run test suite) WARNING: Couldn't find required program qemu (needed to run test suite)

HaLVM Memory Model: 64-bit

I have installed qemu, and there are quite a few qemu-* executables on my system.

I thought xm came from libtif, but that doesn't seemt work either.

I am on Fedora 18, wondering if I might be able to get some support. Thanks!

acw commented 11 years ago

Hi!

I have to admit, I don't quite remember what version of qemu the test suite needs. On the bright (?) side, I don't think the test suite actually works any more, so it shouldn't matter.

'xm' should come from the Xen control tools. It's the command you use to start, list, shutdown, etc., Xen domains, unless they've changed the name of it in recent versions.

johnpmayer commented 11 years ago

Continuing with related issues as I go through the install process: It doesn't appear that any yum packages provide libgmp.so.3, which is required by the build. I used a symbolic link to version 10 as a dirty workaround even though I know that's a bad thing. Is this an expected issue? Perhaps due to the version of ghc?

acw commented 11 years ago

Yes, it's a known issue, having to do with the fact that the GHC we're using is fairly old. Your solution of linking to version 10 will work, at least as far as we have discovered, and is the best solution I'm aware of beyond building your own legacy RPM.

We're hoping to rev the HaLVM to a more modern GHC early next month, which should take care of the problem, but for now a link is still your best bet.

acw commented 11 years ago

This particular issue should be fixed in the 2.0 pre-release. If it isn't, reopen this and tell me, or comment in #14.