Skip to content

Installing mini_racer 0.6 on docker M1 fails with "make: printf: Argument list too long" #272

Description

@diaclavijo

Hello,

I'm working with Docker on M1 Macbook Pro, then when I am trying to update the project from mini_racer 0.4 to 0.6 to support ruby 3.1 it is failing while doing bundle install. See return at bottom.

The problem seems related to libv8-node (16.10.0.0).

On another hand, it works fine while installing it locally (not docker).

...
  touch /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/libv8-node-16.10.0.0/src/node-v16.10.0/out/Release/obj.target/tools/v8_gypfiles/v8_compiler_for_mksnapshot.stamp
make: printf: Argument list too long
make: *** [tools/v8_gypfiles/v8_base_without_compiler.target.mk:1021:
/opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/libv8-node-16.10.0.0/src/node-v16.10.0/out/Release/obj.target/tools/v8_gypfiles/libv8_base_without_compiler.a] Error 127
rm 124a24bf1de8859beea1c6175a3a36094ad7da5b.intermediate e320af0d9616fd7dc4d7dcfabbe4655f4d0793cb.intermediate
make: Leaving directory '/opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/libv8-node-16.10.0.0/src/node-v16.10.0/out'
/opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/libv8-node-16.10.0.0/ext/libv8-node/builder.rb:14:in `build_libv8!': failed to build libv8 16.10.0 (Libv8::Node::BuilderError)
	from /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/libv8-node-16.10.0.0/ext/libv8-node/location.rb:30:in `install!'
	from extconf.rb:9:in `<main>'

extconf failed, exit code 1

Gem files will remain installed in /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/libv8-node-16.10.0.0 for inspection.
Results logged to /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/extensions/aarch64-linux/3.0.0/libv8-node-16.10.0.0/gem_make.out

  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/ext/builder.rb:102:in `run'
  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/ext/ext_conf_builder.rb:28:in `build'
  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/ext/builder.rb:171:in `build_extension'
  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/ext/builder.rb:205:in `block in build_extensions'
  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/ext/builder.rb:202:in `each'
  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/ext/builder.rb:202:in `build_extensions'
  /usr/local/lib/ruby/site_ruby/3.0.0/rubygems/installer.rb:843:in `build_extensions'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/rubygems_gem_installer.rb:71:in `build_extensions'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/rubygems_gem_installer.rb:28:in `install'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/source/rubygems.rb:204:in `install'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/installer/gem_installer.rb:54:in `install'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/installer/gem_installer.rb:16:in `install_from_spec'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/installer/parallel_installer.rb:186:in `do_install'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/installer/parallel_installer.rb:177:in `block in worker_pool'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/worker.rb:62:in `apply_func'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/worker.rb:57:in `block in process_queue'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/worker.rb:54:in `loop'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/worker.rb:54:in `process_queue'
  /opt/helpling/vendor/bundle/ruby/2.6.0/ruby/3.0.0/gems/bundler-2.3.10/lib/bundler/worker.rb:91:in `block (2 levels) in create_threads'

An error occurred while installing libv8-node (16.10.0.0), and Bundler cannot continue.

In Gemfile:
  mini_racer was resolved to 0.6.3, which depends on
    libv8-node
The last command has exited with non-zero code (1280).

Tip: use --help to see all available options

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions