-
Notifications
You must be signed in to change notification settings - Fork 17
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
Gem install nokogiri-xmlsec-instructure failing #15
Comments
Can you help me reproduce this? I'm on an ARM64 Mac, running Ruby 3.1.2, and I have Nokogiri v1.13.8 installed:
|
Here's my nokogiri installation:
|
It looks like the undefined symbols that this gem is looking for are in Nokogiri v1.11.2 and later. You're probably on an older version? |
Hi, thanks for the quick response, this is where I'm at:
It crashes the exact same way as I first wrote, so would it mean it's not compatible with the Nokogiri I have right now? |
@Loschcode Help me reproduce what you're seeing? I am on arm64-darwin and cannot reproduce this. Can you please reply with the output from |
Sorry for that, here's the output
|
Ah, interesting -- I'm using the precompiled nokogiri gem and you're not. I bet that's the reason we're seeing different things. Can you try reinstalling nokogiri but ensure you get the native gem? Run
(note the Then try installing |
(Though I will note that I tried to reproduce by installing Nokogiri from source (not precompiled) and building this gem against it ... and still could not reproduce what you're seeing.) |
Oh yes there's a difference, but you should know it's because I've tried a bunch of things and I did try multiple Nokogiri versions, sadly the result is the same with the
It still crashes for me when trying to install |
I've also tried to install Nokogiri 1.13.8 instead of 1.13.9 and the result is the same 😢 |
I've reinstalled a bunch of libraries with I really can't find a solution for this 😢 I'll keep investigating |
Let's approach this from the other end ... let's look at the symbols in the nokogiri shared object. If you run
Find the gem under that directory, for me it's
Find the shared object for Ruby 3.1 under that directory, for me it's
Run the
The |
Ok so I followed your steps, there's only one version installed
The gem under that directory is
There are shared objects in there, for Ruby 2.6, 2.7, 3.0 and 3.1
This is matching so far. Then I use your command
Then the other command
Seems like everything is in place 😢 thanks for your time by the way, it's really nice to see your quick responses 👍 |
That's really strange. Can you double-check for me what the errors are during build against 1.13.9? The original post listed:
but I can't make sense of that unless that log is from a build against a much older version (as mentioned earlier). |
It outputs exactly this, so the same
I'm really confused as well, everything is as I showed |
🤔 Can you reply with the contents of the |
Regarding the
And the
|
Can you please also reply with the |
Hi, here's the
|
Ah, OK, here's a big difference between my Makefile and yours, and I believe it's related to how your Ruby was configured when it was built and installed. On MacOS, clang will not allow any unresolved symbols at link time (some discussion which explains a bit more is at this SO post) unless the linked is explicitly told to with a flag like On my machine, this is present in
This flag doesn't appear in your Makefile, and I think that's the reason this is happening to you and not to me. When I remove that flag from my Makefile and build, I see the same error as you:
There doesn't seem to be an easy workaround, the Makefile doesn't allow injection of additional linker flags via environment variables as far as I can tell. Can you say a bit about how your Ruby was built? |
Well, I just used |
On my M1 I use https://github.com/postmodern/ruby-install (which you can install with homebrew) to install Rubies from source. |
There's a potentially related thread right now in the https://bugs.ruby-lang.org/issues/18912 In any case, you may want to make sure your Ruby is built with the |
I've tried installing ruby through
Also I've tried downgrading to Xcode 13.4 because it's what your link recommend, but it fails too
I feel really stuck and unlucky, I'll try out the |
I've tried to reinstall Ruby through |
Big news today, after investigating further and going through this link, I could build your gem with this command
Not sure what those exact flags mean, I just copied it from the issue, but it's progress. Now I've to see how to do the same through |
For anyone interested and facing this problem, the solution to
|
@flavorjones thanks for following up with this problem and being super reactive, that helped me a lot. Cheers 🤘 happy Halloween and have a good week! |
Great! I'm glad you found a workaround. Thanks for closing the loop! |
FYI |
This fixed this issue for me tysm! I was running out of hair to pull out |
On ARM64, I can't find a way to make it work. I've looked everywhere and tried to find workarounds such as reinstalling XCode, reinstalling entirely Ruby, reinstalling a bunch of libraries with
brew
Any idea what's going on here?
The text was updated successfully, but these errors were encountered: