Notes about issue ruby_mkmf_makefile_unsorted_objects in buster
Identifier: | ruby_mkmf_makefile_unsorted_objects |
---|---|
Suites: | unstable / trixie / bookworm / bullseye / buster / experimental |
URL: | https://bugs.debian.org/825569 |
Description: |
Ruby projects which also include C sources and use create_makefile from mkmf.rb (typically in ext/.../extconf.rb) will be unreproducible, because the list of object files in the generated Makefile is unsorted. . Many of those packages are likely affected: https://codesearch.debian.net/perpackage-results/path%3Aextconf.rb%20create_makefile/2/page_0 . ruby: https://sources.debian.net/src/ruby2.3/latest/lib/mkmf.rb/#L2180 jruby: https://sources.debian.net/src/jruby/latest/lib/ruby/shared/mkmf.rb/#L1488 |
Packages in 'buster' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
None |
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A #
sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+
sign indicates there is a
patch available, a P
means a
pending bug while #
indicates a
closed bug. In cases of several bugs, the symbol is repeated.