Bug #21779: Do not export functions from statically linked extensions

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.2: REQUIRED, 3.3: DONE, 3.4: DONE

[nobu (Nobuyoshi Nakada)]

Reported at https://github.com/ruby/io-console/pull/105.

This is caused by InitVM_console exposed from the statically linked io/console is called from the loaded io-console gem.
The static InitVM_console initializes the ractor local storage key, but it is different from the key used in the gem extension.

Also, the workaround for conflict between Init functions is necessary for InitVM functions too.

https://github.com/ruby/ruby/pull/15539

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset git|bc2a8a002a6c41fc1b28e02e15e2fb2b72d1b66e.

---

[Bug #21779] Uniquify InitVM functions as well as Init

Avoid possible name conflict when --with-static-linked-ext.

[k0kubun (Takashi Kokubun)]

• Backport changed from 3.2: REQUIRED, 3.3: REQUIRED, 3.4: REQUIRED to 3.2: REQUIRED, 3.3: REQUIRED, 3.4: DONE

ruby_3_4 252b718582baf5760a6db2efdb58b84a0bf3f47f merged revision(s) bc2a8a002a6c41fc1b28e02e15e2fb2b72d1b66e, c26057ebafb23b063190d31d5b4d19a0e0a1306c.

[hsbt (Hiroshi SHIBATA)]

• Backport changed from 3.2: REQUIRED, 3.3: REQUIRED, 3.4: DONE to 3.2: REQUIRED, 3.3: DONE, 3.4: DONE

ruby_3_3 7cb33b6a88beda081c9fd56302ee403333ba4427 merged revision(s) bc2a8a002a6c41fc1b28e02e15e2fb2b72d1b66e, c26057ebafb23b063190d31d5b4d19a0e0a1306c.