From: "knu (Akinori MUSHA)" Date: 2021-10-21T09:41:29+00:00 Subject: [ruby-core:105725] [Ruby master Feature#17760] Where we should install a header file when `gem install --user`? Issue #17760 has been updated by knu (Akinori MUSHA). We have discussed this in today's developer meeting. - As a tentative workaround, I'll fix the digest gem not to try to install `digest.h` to an unwritable directory so `gem install --user digest` succeeds. - It is (technically) possible for RubyGems to specify where to install header files by passing `HDRDIR=destination` to `make install` for example, and to expose the installed header files of activated gems to a newly built gem by passing `CPPFLAGS` to `extconf.rb` that lists the header directories. ---------------------------------------- Feature #17760: Where we should install a header file when `gem install --user`? https://bugs.ruby-lang.org/issues/17760#change-94224 * Author: mrkn (Kenta Murata) * Status: Third Party's Issue * Priority: Normal ---------------------------------------- As `digest` have been made a default gem at Ruby 3.0, it can be installed by `gem install` command. When we install `digest`, `digest.h` is installed at the same directory as `ruby.h`. But when we use `gem install --user` for installing it, where should `digest.h` is installed in? Now, the location of `digest.h` is always the same directory as `ruby.h` regardless of whether we use `gem install --user`. It occurs permission error when non-root user uses `gem install --user` for installing `digest` on the system-ruby. -- https://bugs.ruby-lang.org/ Unsubscribe: