Skip to content
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.

"illegal hardware instruction" on install command #271

Open
gutierlf opened this issue May 22, 2017 · 3 comments
Open

"illegal hardware instruction" on install command #271

gutierlf opened this issue May 22, 2017 · 3 comments

Comments

@gutierlf
Copy link

I've tried installing Elm 0.18.0 via npm and via the Mac installer. In both cases, I can't get elm-package install to download packages for me.

> mkdir test-example
> cd test-example
> elm-package install
Some new packages are needed. Here is the upgrade plan.

  Install:
    elm-lang/core 5.1.1
    elm-lang/html 2.0.0
    elm-lang/virtual-dom 2.0.4

Do you approve of this plan? [Y/n] Y
Starting downloads...

[1]    65368 illegal hardware instruction  elm-package install

(That's the error message when using the version installed via the Mac installer. When using the npm-installed version, there was no illegal hardware instruction error; it was just completely silent.)

@agrafix's python script found in #115 does work and allows me to install packages one-by-one, but I don't know how that script is different than what elm-package install does.

My configuration:
OS X 10.11.6
2.2 GHz Intel Core 2 Duo
Elm 0.18.0

@process-bot
Copy link

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

@evancz evancz changed the title elm-package install fails silently "illegal hardware instruction" on install command Jul 11, 2017
@evancz
Copy link
Contributor

evancz commented Jul 11, 2017

Can you say more about your system? Is there anything notable? Any odd hardware? Any weird configuration?

I would expect to hear much more about this issue if lots of folks were seeing it, so I strongly suspect there is something unlikely about your system.

@gutierlf
Copy link
Author

Thanks for following up on this!

This also surprised me initially, but then when I found the other issues that I mentioned above, including a python script workaround, I thought, "well maybe this old bug just popped up again."

In any case, I'll try to answer your question about my configuration. I'm only answering from memory right now because I'm not in front of my computer, and I'll add more later if I find something. However, I don't think I'm doing anything weird with this machine. No additional hardware. That said, it's an old machine that I just found and wiped clean a couple months before trying out Elm. Because it's not very powerful, I've tried to keep it pretty vanilla, with few additional apps or frameworks installed.

Are there any specific parts of my configuration that you're suspicious about where I might look more carefully? Or anything I can do to generate more verbose log information that might prove more useful in getting to the bottom of this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants