On Tue, May 11, 2021 at 06:33:07PM -0800, Christopher Howard wrote:
> As a guess, I suspect your build made use of some advanced multimedia
> CPU flag not available on my computer.
I'd guess that the problem is that it's being built with -march=native,
which the build logs show.
We'll need to dis
This is the build log from the server. there may be clues here if it differs
from yours:
https://ci.guix.gnu.org/build/290428/log/raw
Hello, I ran the following:
guix gc -D $(guix build --no-grafts vice); guix build --no-substitutes
vice
guix challenge vice
The result of the last command was
/gnu/store/ixsr68sfkyfvp66mzg6291sv2gbdwvzc-vice-3.5 contents differ:
local hash: 1gw2m26g506fivlki829h4ljjxs4s6c4c9hyi8bdzl1h4kw4qz6l
I'm curious the guix version would also build differently on your computer.
You can run for example
guix build vice --no-grafts --check
to build it from source and check the difference. if its different, something
like
guix gc -D $(guix build --no-grafts vice); guix build --no-substitutes vice
Comparing objdumps on the guix binary vs. my local binary, I suspect
that the extension available on your CPU but not on mine is the AVX*
instructions. I see that, e.g., VMOVAPS is used in your binary, but
that is not available on my system.
https://www.felixcloutier.com/x86/movaps
some diff outp
Hi, when I install vice from guix, and attempt to run a ROM, I get this
error, and the GUI does not launch:
Illegal instruction
However, if I pull the source with `guix -S vice', create a build
environment with `guix environment vice', and build it myself (with
./configure --prefix=/home/christop
