Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#62244 closed defect (fixed)

ruby19, rb19-rufus-mnemo, rb19-saikuro: It seems your ruby installation is missing psych (for YAML output).

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: jmroot (Joshua Root)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: kimuraw (kimura wataru)
Port: ruby19, rb19-rufus-mnemo, rb19-saikuro

Description

rb19-rufus-mnemo and rb19-saikuro at least fail to build on macOS 11:

/opt/local/lib/ruby1.9/1.9.1/yaml.rb:84:in `<top (required)>':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
ERROR:  Loading command: install (LoadError)
    cannot load such file -- zlib
ERROR:  While executing gem ... (NameError)
    uninitialized constant Gem::Commands::InstallCommand

Not sure if a bug in those ports or in ruby19. ruby19 does declare a dependency on libyaml, but maybe it is the well-known problem with implicit function declarations in Xcode 12 and later that has prevented ruby19 from seeing libyaml (although I'm not able to verify that).

Change History (4)

comment:1 Changed 3 years ago by jmroot (Joshua Root)

Yes, there are lots of implicit declaration errors. The code that looks for those in master doesn't catch them, both because they happen in the build phase and because they are in files called mkmf.log.

comment:2 Changed 3 years ago by jmroot (Joshua Root)

Owner: set to jmroot
Resolution: fixed
Status: newclosed

In 2a18c987332e68725eca840a3bebdf783f082e2d/macports-ports (master):

ruby19: fix missing extensions

Closes: #62244

comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Thanks. I didn't check if other ruby versions are affect too.

comment:4 Changed 3 years ago by jmroot (Joshua Root)

I'd be surprised if the other ruby ports didn't have similar issues. It looks like 2.0 and later have a bundled libyaml that they use if the system one isn't found, which would prevent this particular error.

Note: See TracTickets for help on using tickets.