Opened 7 months ago
Last modified 7 months ago
#69410 assigned defect
rb*-unf_ext tries to link against libstdc++ on 10.7–10.12 with clang
Reported by: | barracuda156 | Owned by: | barracuda156 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.1 |
Keywords: | lion, mountainlion, mavericks, yosemite, elcapitan, sierra | Cc: | |
Port: | rb-unf_ext |
Description
For w/e reason, wrong C++ runtime is picked by the build on 10.7–10.12: https://github.com/knu/ruby-unf_ext/issues/79
Change History (2)
comment:1 follow-up: 2 Changed 7 months ago by kencu (Ken)
comment:2 Changed 7 months ago by barracuda156
Replying to kencu:
probably
https://github.com/knu/ruby-unf_ext/blob/c72a36d0a5ea9fe3950611b0f289fc68a2595fcf/Rakefile#L15
looks like that might be overridden by a config option.
I would assume that -lstdc++
is not linking to a static version, which Rakefile
seems to refer, but I know close to nothing about how Ruby gem build system works, so no idea.
An odd thing is why whatever is broken gets triggered only for a subset of systems.
Note: See
TracTickets for help on using
tickets.
probably
https://github.com/knu/ruby-unf_ext/blob/c72a36d0a5ea9fe3950611b0f289fc68a2595fcf/Rakefile#L15
looks like that might be overridden by a config option.