| Age | Commit message (Collapse) | Author |
|
|
|
|
|
`.bundle/specification/foo-x.y.z.gemspec` may be changed our toolchain
|
|
|
|
|
|
This reverts commit 76c61c9993e59af0b4c400b44f169f4af99c3efa.
|
|
|
|
Try to install also gemspec files under gem directories
Gemspec files having extension libraries are placed under each gem
directories now.
---
tool/rbinstall.rb | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
|
|
Stop `build_extensions` when DESTDIR set
Try to fix `make install without root privilege` failures on snapshot CIs.
example: https://github.com/ruby/actions/actions/runs/2315349280
---
tool/rbinstall.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
rbinstall: Also do `Gem.ruby` patching for unpacked bundled gems
Pointing `Gem.ruby` to the newly installed ruby gives mkmf the right
inputs to build extensions in bundled gems. Previously, this patching
was only done for compressed bundled gems.
This patch also prevents `tool/fake.rb` from propagating to the child
process running mkmf for the native extension. The way `tool/fake.rb`
changes mkmf variables using `Kernel#trace_var` created spooky action at
a distance which made debugging difficult.
AppVeyor Windows CI started to fail starting with
8a3663789c52ec5635194656af6b69d3d03120ee because it enabled extension
building for bundled gems on mswin. This patch should address the CI
failures.
---
tool/rbinstall.rb | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
|
|
Fix bundled gems installation when relative loading
---
tool/rbinstall.rb | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
|
|
Skip build extensions again on cross compiling too
---
tool/rbinstall.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
Skip build extensions again on mswin and mingw
---
tool/rbinstall.rb | 3 +++
1 file changed, 3 insertions(+)
|
|
Enabled to build extensions with the bundled gems again
https://github.com/ruby/ruby/commit/cbb115213c42f15638ef119eb20c4d3106eb8b1a
https://github.com/ruby/ruby/commit/5c1b76a3a55afeb07116bbd3492303c6b6cd890d
---
tool/rbinstall.rb | 3 ---
1 file changed, 3 deletions(-)
|
|
Install built gem extension binaries
---
tool/rbinstall.rb | 56 ++++++++++++++++---------------------------------------
1 file changed, 16 insertions(+), 40 deletions(-)
|
|
This reverts commit bda0b8c09331111f38af98291c201595ce3a2872.
|
|
|
|
[Backport #18373]"
This reverts commit d56b2e8820efd40840443ce3a5d16cff32a090c7.
|
|
Install built gem extension binaries
---
tool/rbinstall.rb | 56 ++++++++++++++++---------------------------------------
1 file changed, 16 insertions(+), 40 deletions(-)
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5297
|
|
Install bundled gem extension files to the gem extension directory
under DESTDIR, when static-linked-ext as well as non-static case.
Notes:
Merged: https://github.com/ruby/ruby/pull/5308
|
|
When building with --with-static-linked-ext, some exts without rb file
doesn't produce neither .so or .rb under .ext/common. Therefore, change
rbinstall.rb to install gemspec even if there is no .so or .rb for that
case.
Notes:
Merged: https://github.com/ruby/ruby/pull/5206
|
|
With /Z7, no .pdb file is generated, so trying to link it during build
fails on my machine even though it's okay on CI.
By the way, in my local testing, no .pdb is generated in cwd at runtime
even without the /Fd option. I guess we can pass it just in case.
Notes:
Merged: https://github.com/ruby/ruby/pull/5058
|
|
.. mainly to fix emscripten CI
http://rubyci.s3.amazonaws.com/crossruby/crossruby-master-wasm64_emscripten/log/20211104T024621Z.fail.html.gz
Notes:
Merged: https://github.com/ruby/ruby/pull/5078
|
|
Since these regexps are used at build/installation, they are not
vulnerabilities.
Notes:
Merged: https://github.com/ruby/ruby/pull/5056
|
|
For the `test-bundled-gems`, make `debug.so` with extconf.rb and
`make` command directly because `rake-compiler` assume ruby is
installed (but `test-bundled-gems` can run without installation).
Notes:
Merged: https://github.com/ruby/ruby/pull/4804
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4804
|
|
|
|
|
|
|
|
|
|
Remove GNU make `-O` and `-W` options which are short but followed
by an argument, so that `$mflags.set?(?n)` does not return `true`
wrongly.
|
|
|
|
[Bug #17476][ruby-core:101724]
|
|
|
|
|
|
|
|
To uniform directory structures, sometimes files are gathered in
different directory than the upstreams, executable files in
`libexec` for instance. Re-map these files to consistent with the
upstreams.
|
|
Because unexpected names are listed in gemspec files.
* "Fix gemspec only case"
fc56b96b09e477686975c978142e3af9179219cd
* "Refined installation of gemspecs placed other than ext and lib"
31f4dec6373c15a58899f8b86e35d48a7d813bf6
|
|
Use UnpackedInstaller for installation of default gems similarly it is
already used to install bundled gems.
This allows to reuse RubyGems functionality instead of custom code full
of exceptions.
|
|
|
|
|
|
|
|
|
|
Not to be overwritten by test-bundler-prepare. gem files often
contain useless gemspec files which have not been processed.
|
|
did_you_mean splits the output by `$/`.
|
|
As `spec.files` is used for `executables` and so on, the expanded
list needs to be located at the same place.
|
|
Although gemspec file (e.g., power_assert and rake) often uses
`git ls-files`, as it does not make sense in other than its own
repository, it has been ignored now. Gather all files expanded
from the bundled gem to install, instead.
|
|
Since 6f3e8df133c7785ff6bb6f18d1faec81fefb3999 in 2014.
|
|
|