@sam I’m consistenly getting this error when running bundle install after therubyracer was replaced with mini_racer. Gem::Ext::BuildError: ERROR: Failed to build gem native extension. /usr/bin/ruby2.2 -r ./siteconf20160523-1400-1x811sw.rb extconf.rb checking for main() in -lpthread... yes creating Makefile make "DESTDIR=" clean make "DESTDIR=" compiling mini_racer_extension.cc In file included from mini_racer_extension.cc:4:0: /var/lib/gems/2.2.0/gems/libv8-5.0.71.48.3-x86-linux/vendor/v8/include/v8.h:341:1: error: expected unqualified-id before ‘using’ /var/lib/gems/2.2.0/gems/libv8-5.0.71.48.3-x86-linux/vendor/v8/include/v8.h:477:1: error: expected unqualified-id before ‘using’ /var/lib/gems/2.2.0/gems/libv8-5.0.71.48.3-x86-linux/vendor/v8/include/v8.h:871:1: error: expected unqualified-id before ‘using’ mini_racer_extension.cc:136:51: error: ‘Handle’ has not been declared mini_racer_extension.cc:136:57: error: expected ‘,’ or ‘...’ before ‘<’ token mini_racer_extension.cc: In function ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’: mini_racer_extension.cc:140:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:144:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:148:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:152:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:156:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:160:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:165:55: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc:171:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:175:9: error: ‘value’ was not declared in this scope mini_racer_extension.cc:184:53: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc:186:57: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc:193:26: error: ‘value’ was not declared in this scope mini_racer_extension.cc: At global scope: mini_racer_extension.cc:197:8: error: ‘Handle’ does not name a type mini_racer_extension.cc: In function ‘VALUE rb_context_eval_unsafe(VALUE, VALUE)’: mini_racer_extension.cc:299:61: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc:306:63: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc:348:56: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc: In function ‘void* gvl_ruby_callback(void*)’: mini_racer_extension.cc:396:2: error: ‘Handle’ was not declared in this scope mini_racer_extension.cc:396:17: error: expected primary-expression before ‘>’ token mini_racer_extension.cc:396:19: error: ‘external’ was not declared in this scope mini_racer_extension.cc:396:45: error: expected primary-expression before ‘>’ token mini_racer_extension.cc:396:46: error: ‘::Cast’ has not been declared mini_racer_extension.cc:409:65: error: cannot convert ‘v8::Local ’ to ‘int’ for argument ‘2’ to ‘VALUE convert_v8_to_ruby(v8::Isolate*, int)’ mini_racer_extension.cc:430:2: error: ‘Handle’ was not declared in this scope mini_racer_extension.cc:430:14: error: expected primary-expression before ‘>’ token mini_racer_extension.cc:430:16: error: ‘v8_result’ was not declared in this scope mini_racer_extension.cc:430:73: error: ‘convert_ruby_to_v8’ was not declared in this scope make: *** [mini_racer_extension.o] Error 1 make failed, exit code 2 Gem files will remain installed in /tmp/bundler20160523-1400-1fbh6n7/mini_racer-0.1.3/gems/mini_racer-0.1.3 for inspection. Results logged to /tmp/bundler20160523-1400-1fbh6n7/mini_racer-0.1.3/extensions/x86-linux/2.2.0/mini_racer-0.1.3/gem_make.out An error occurred while installing mini_racer (0.1.3), and Bundler cannot continue. Make sure that `gem install mini_racer -v '0.1.3'` succeeds before bundling.

Just formated one of my disks, using Gnome Ubuntu 16.04. After that it’s more or less following this. Just: changing ruby version (2.0.0-turbo → 2.3.1) postgresql verison (9.3 → 9.5) creating the databases with my user as owner using a ppa for redis and installing image_optim dependencies as described here so that pesky warnings disappear from running the specs.

Should we update that? Can you PR changes and I will add them?

Yes for sure! This is way better than vagrant!

I’m in the process of setting up a dev environment on a new system and ran across this thread after a problem with mini_racer - I’m using GNU/Linux. While I agree with @Falco that developing natively is faster, I think the advantages of Vagrant are huge and should be preserved. I’m in the process of making an image that uses Ubuntu 16.04 (based on 16.04 Server iso) and has a few steps fixed. I’ll submit it when done. Also, I am modifying the Vagrantfile with the following: Removing the NFS dependency (it confuses GNU/Linux hosts, and is not necessary as far as I can tell) Adds instructions from Discourse as your first Rails app and Preparing a fresh Ubuntu install so they are run when Vagrant provisions the first time The end result will be a fully functional discourse when the person first types vagrant up. I’ll submit it as a PR when ready. I’ll upload the image to a public dropbox, though obviously it would be better if somebody from discourse uploaded it where the old image is.

You could also check Docker image file for provisioning right version as Vagrant is meant to uniform production & dev env :slight_smile:

Your not the only one that has had issues so welcome this :slight_smile: Currently working my way through this one [image] Install Discourse on Ubuntu or Debian for Development Developer Guides warning This guide covers installation instructions in a development environment. For a production guide see: Install Discourse in production with the official supported instructions So you want to set up Discourse on Ubuntu or Debian to hack on and develop with? We’ll assume that you work locally and don’t have Ruby/Rails/Postgres/Redis installed on your Ubuntu or Debian system. Let’s begin! Requirements We suggest having at least 4 GB RAM and 2 CPU cores. Current compatibility: O…

Honestly, it doesn’t make sense to have to install to a system each time. I frequently hop between systems and Vagrant has made developing incredibly easy - just vagrant up and go. No reason we can’t accomplish that here. I’m well on my way to getting the image prepared with 16.04 server. Just configuring it now then I’ll upload.

I have submitted a pull request that results in a fully configured Discourse development environment. The Ubuntu .box file is uploaded to dropbox, but can be adopted by @codinghorror or @sam for their own uses.

Well, I’ll admit I did a bit of muttering under my breath when my dev set up broke after the last upgrade. (“a set up a few versions behind would be better than no set up at all” being one of the more polite thoughts) Having used a Windows - Github - VirtualBox - Vagrant set up for over a year, I wasn’t too keen on getting something set up again. I eventually installed VMware Player, downloaded the Ubuntu desktop iso and got that working. Then it took a while to learn my way around Ubuntu. It sure ain’t the Windows UI that I’m used to. Installed Docker, Cloned Discourse. I struggled with getting Windows and Ubuntu to “talk” with each other for quite a while. Several failed “share” attempts later I finally installed VMware Tools and VMware Tools Desktop and managed to import and restore my last backup. I still want to figure out the sound card issue, but after only a couple of days, I don’t miss Vagrant at all. Many of the problems I had had with Vagrant for so long that I just accepted them as “thats the way it is” are gone. And working with VMware Player is very easy now that I’ve learned its UI. For those still hanging on to Vagrant I recommend you give VMware a try.

I tried updating to trusty using do-release-upgrade, as @angus suggested. Following the update and “restart”, I can’t use vagrant up`. It fails with: Failed to mount folders in Linux guest. This is usually because the "vboxsf" file system is not available. Please verify that the guest additions are properly installed in the guest and can work properly. The command attempted was: mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant-root /vagrant mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant-root /vagrant The error output from the last command was: stdin: is not a tty /sbin/mount.vboxsf: mounting failed with the error: No such device Edit: this is in Vagrant on an OSX system.

Mini_racer installation issues on ubuntu vagrant (OSX)

Development

mikechristopher June 2, 2016, 10:53am 20

Your not the only one that has had issues so welcome this

Currently working my way through this one

Topic		Replies	Views
Mini_racer breaks build on latest-release Product Support unsupported-install	2	1476	April 29, 2019
Chat not working after dev install Product Support dev-install , chat	21	623	February 27, 2025
Mini_racer 0.2.0 causing bundler to fail Self-hosting unsupported-install	1	2015	January 11, 2019
Mini_racer causing rebuild fail Bug	11	3928	November 4, 2016
Bundler cannot continue due installation error of mini_racer 0.4.0 Development	1	3306	June 17, 2021

Mini_racer installation issues on ubuntu vagrant (OSX)

Related topics