Bug #18997: Don't define ruby_qsort when POSIX qsort_r is available

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: Not applicable
• Backport: 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED

[delphij (Xin Li)]

The current code would define ruby_qsort as a wrapper of qsort_s when it is available. When both qsort_s and POSIX (GNU) qsort_r are available, we should call qsort_r directly instead, and the qsort_s wrapper is redundant.

Proposed patch at https://github.com/ruby/ruby/pull/6332 and can be applied on Ruby 2.7 and newer Ruby versions

[nobu (Nobuyoshi Nakada)]

• Backport changed from 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED

• Status changed from Open to Closed

Applied in changeset git|7400628cb054a9a9651d69411a100fc9d518099f.

---

[Bug #18997] Don't define ruby_qsort when POSIX qsort_r is available

The current code would define ruby_qsort as a wrapper of qsort_s
when it is available. When both qsort_s and POSIX (GNU) qsort_r
are available, we should call qsort_r directly instead, and
the qsort_s wrapper is redundant.

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED

I don't think this is necessary to backport to stable branches.

[nobu (Nobuyoshi Nakada)]

• Related to Bug #20151: Can't build Ruby 3.1 on FreeBSD 14.0 added