Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intel Mac -- Arm64 Nokogiri... #60

Open
wookdev opened this issue Feb 20, 2022 · 1 comment
Open

Intel Mac -- Arm64 Nokogiri... #60

wookdev opened this issue Feb 20, 2022 · 1 comment

Comments

@wookdev
Copy link

wookdev commented Feb 20, 2022

Put it in my Gemfile, and it apparently installed there okay:

Installing racc 1.6.0 with native extensions
Fetching nokogiri 1.13.1 (x86_64-darwin)
Fetching nokogiri 1.13.1 (arm64-darwin)
Installing nokogiri 1.13.1 (x86_64-darwin)
Installing nokogiri 1.13.1 (arm64-darwin)
Fetching jekyll-target-blank 2.0.0
Installing jekyll-target-blank 2.0.0
Bundle complete! 9 Gemfile dependencies, 55 gems now installed.
Bundled gems are installed into `./.vendor/bundle`

Run Jekyll serve, and it blows up. The relevant error from the stack trace is:

dlopen(/Users/wook/projects/munged-org/.vendor/bundle/ruby/2.6.0/gems/nokogiri-1.13.1-arm64-darwin/lib/nokogiri/2.6/nokogiri.bundle, 0x0009):
tried: '/Users/wook/projects/munged-org/.vendor/bundle/ruby/2.6.0/gems/nokogiri-1.13.1-arm64-darwin/lib/nokogiri/2.6/nokogiri.bundle'
(mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64h')), '/usr/lib/nokogiri.bundle' (no such file)
 - /Users/wook/projects/munged-org/.vendor/bundle/ruby/2.6.0/gems/nokogiri-1.13.1-arm64-darwin/lib/nokogiri/2.6/nokogiri.bundle (LoadError)

As it says, I have a intel MacBook Pro. Not sure why it's calling the arm64 executable.

If I delete the arm64 nokogiri gem, then it seems to work. But any use of bundle install or bundle update puts it right back in place, which is kinda annoying. I've not found a way to exclude that gem in the Gemfile. No idea how to force it to use the right one, if that's even possible.

@prplecake
Copy link
Contributor

This seems to be an issue with nokogiri as opposed to jekyll-target-blank.

Check these issues, the first has a few commands you can try to force the correct gem architecture:

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

No branches or pull requests

2 participants