You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Admin-OneClick:~/environment $ brew gem install cfn-nag
==> Fetching gem-cfn-nag
==> Fetching cfn-nag from gem source
Fetching cfn-nag-0.8.10.gem
Downloaded cfn-nag-0.8.10
Warning: Cannot verify integrity of 'cfn-nag-0.8.10.gem'.
No checksum was provided.
For your reference, the checksum is:
sha256 "052aea03f2cd92ff34ea51a2e8fe287b4489dc4c57f04d1ca6e5855fe325d333"
==> /home/linuxbrew/.linuxbrew/opt/ruby/bin/gem install /home/ec2-user/.cache/Homebrew/cfn-nag-0.8.10.gem --no-document --no-wrapper --no-user-install --install-dir /home/linuxbrew/.linuxbrew/Cellar/gem-c
Last 15 lines from /home/ec2-user/.cache/Homebrew/Logs/gem-cfn-nag/01.gem:
from /home/linuxbrew/.linuxbrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/mkmf.rb:1209:in `find_header'
from extconf.rb:10:in `<main>'
To see why this extension failed to compile, please check the mkmf.log which can be found here:
/home/linuxbrew/.linuxbrew/Cellar/gem-cfn-nag/0.8.10/extensions/x86_64-linux/3.2.0/psych-3.3.4/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in /home/linuxbrew/.linuxbrew/Cellar/gem-cfn-nag/0.8.10/gems/psych-3.3.4 for inspection.
Results logged to /home/linuxbrew/.linuxbrew/Cellar/gem-cfn-nag/0.8.10/extensions/x86_64-linux/3.2.0/psych-3.3.4/gem_make.out
A new release of RubyGems is available: 3.4.10 → 3.4.13!
Run `gem update --system 3.4.13` to update your installation.
Do not report this issue to Homebrew/brew or Homebrew/homebrew-core!
Admin-OneClick:~/environment $
On Cloud9 there is even a log at /home/linuxbrew/.linuxbrew/Cellar/gem-cfn-nag/0.8.10/extensions/x86_64-linux/3.2.0/psych-3.3.4/mkmf.log.
Tested on both WSL Linux and Cloud9:
On Cloud9 there is even a log at
/home/linuxbrew/.linuxbrew/Cellar/gem-cfn-nag/0.8.10/extensions/x86_64-linux/3.2.0/psych-3.3.4/mkmf.log
.On WSL it gives:
The text was updated successfully, but these errors were encountered: