-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
[macOS][11.4] ERROR: Error installing byebug 11.1.3 #822
Comments
I worked around this by using an up-to-date C compiler: % echo $CC $CXX
% gcc --version
# Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
# Apple clang version 12.0.5 (clang-1205.0.22.11)
# Target: x86_64-apple-darwin20.6.0
# Thread model: posix
# InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
% export CC=gcc-11 CXX=g++-11
% g++-11 --version
# g++-11 (Homebrew GCC 11.2.0) 11.2.0
# Copyright (C) 2021 Free Software Foundation, Inc.
# This is free software; see the source for copying conditions. There is NO
# warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
% gem install byebug
# Building native extensions. This could take a while...
# Generating ctags for byebug-11.1.3
# Successfully installed byebug-11.1.3
# Parsing documentation for byebug-11.1.3
# Installing ri documentation for byebug-11.1.3
# Done installing documentation for byebug after 10 seconds
# 1 gem installed |
For me it fails with ruby 3.0 but works with ruby 3.1 in nix (without exporting any variables or changing anything). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
gem install byebug -v '11.1.3' --source 'https://rubygems.org/'
Expected behavior
I expected that the gem would install successfully.
Actual behavior
The full transcript can be found here:
Steps to reproduce the problem
Steps:
The text was updated successfully, but these errors were encountered: