The section has grown past building with the crash dumps, so give it its own page next to building and testing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The CI uploads crash dumps on Windows, Linux and macOS now, and a crash that leaves no [BUG] report can only be followed through one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The premature `ruby` link it warned about comes from `programs` running
before `exts` under `make test-all`, not from parallelism, and whether
the extension build repairs it afterwards varies. Documenting a make
version is the wrong place to address it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The option was described only by configure --help, so the extra
--with-EXTLIB-dir options it needs had to be found by trial and error.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Clarify “Building Ruby” docs
* Fix test examples to work from `build` dir
* Clarify “Testing Ruby” examples with real examples
All the commands should run correctly by default, without the user needing to modify them. This builds confidence that the relative paths are working correct from within the `build` directory.
Also, let’s use a consistent example throughout, for greater clarity.
* Improve examples to use `-v` flag in-context
This shows the correct way to combine `-v` with another parameter, e.g. a specific file to test.
* Other readability improvements
* Clarify `make` implementation support
* Fix WASM bullet/code indentation
* Use `console` code highlighting where appropriate
… which handles the prefix `$` correctly.
* Migrate feature proposal template to MarkDown
* Set language on code blocks
I don't really think ASAN works well at all on any version of Ruby from
before https://bugs.ruby-lang.org/issues/20001 was landed. Update the
docs to clarify what works, and what does not work.
Also there's no need to compile at `-O0`; this was probably just hiding
some of the problems with our stack scanning that were fixed in the
above issue.
[Bug #20248]
[Misc #16671]
I'd like to bump it to 2.7 to use pattern matching in
tool/mk_builtin_loader.rb.
However, I experienced a few blockers. 2.5 seems like the closest
version that is easy enough to use on CIs, so let me bump the version to
it as an intermediate step for it. I want to use &. and <<~ in 2.3 too.
Known blockers:
* AppVeyor Visual Studio 2015 doesn't have Ruby 2.7. You'd need to bump
the version to Visual Studio 2019.
* GitHub Actions windows-2019 doesn't have Ruby 2.7 either. You
can use ruby/setup-ruby, but configure doesn't seem to work with it.
* For ruby/ruby-ci-imaage, bionic doesn't have Ruby 2.7. I tried using
ruby-build to build Ruby 2.7 from package, but the build on its CI
seems to somehow loop forever when I do that. So I gave it up for now.
We might want to wait until bionic becomes EOL.
Note:
* AppVeyor Visual Studio 2015 has Ruby <= 2.6.3
https://www.appveyor.com/docs/windows-images-software/#ruby
* GitHub Actions windows-2019 uses Ruby 2.5.9
https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md
The command line arguments to `configure` are stored in `rbconfig.rb`.
Usually these are just useless but harmless after the installation,
however could affect unexpectedly when updating default gems.
