Skip to content

build: keep the linker options of a gem that is in libmruby.a #7203

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.

Sign up for GitHub

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

Merged
matz merged 1 commit into from
Aug 16, 2026
Merged

build: keep the linker options of a gem that is in libmruby.a #7203

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions lib/mruby/gem.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -648,8 +648,12 @@ def import_include_paths(g)
end

def linker_attrs(gem=nil)
gems = self.reject{|g| g.bin?} # library gems
gems << gem unless gem.nil?
# A gem that puts no object in libmruby.a contributes nothing to a link
# of it, so its linker options are its own binary's alone; ref #5210.
# One that does put objects there needs its options wherever libmruby.a
# is linked, whether or not it builds a binary as well.
gems = self.reject{|g| g.bin? && g.objs.empty?}
gems << gem unless gem.nil? || gems.include?(gem)
gems.map{|g| g.linker.run_attrs}.transpose
end
end # List
Expand Down
Loading