I installed rhostudio but I can't seem to install the gems using the provided scripts.
I get
Last login: Sat Mar 24 13:43:13 on ttys001
jay-pc:~ mac$ /Volumes/RhoInstaller/Install\ gems ; exit;
Please install building tools
logout
I'm a new ruby dev...
I don't know if this is referring to java or make etc. Or something ruby or gems specific.
I have jdk installed as I use the machine for java development.
Okay yes - birryree mentioned above that xcode is needed. This is the answer. It's actually the Gnu Compiler Collection that is required so if you don't care about getting xcode you can just download the osx GCC from here to save some bandwidth:
(lion here too)
https://github.com/kennethreitz/osx-gcc-installer
Related
What are some less painful ways to install Ruby on AIX?
I found out that using RVM to install Ruby might be the best option. However, installing RVM itself seems like really maddening. I found an article from IBM website on how to install RVM but there are so many prerequisites for it that I feel like it will take me days to get all that stuff installed and get working:
However, RVM does have some prerequisites. Before you continue, check your system and be sure that you have the bash, git, tar, curl, gunzip, and bunzip2 utilities installed locally. In addition, your system must have the Readline, IConv, zLib, OpenSSL, and Autoconf packages to build the Ruby interpreters. You must have the Bash shell to install RVM, but you can use RVM with the Z shell version 4.3.5 or higher after RVM is installed. git is required to automatically update RVM, and this is explained shortly.
I looked up git and it has at least 10 prerequisites (includes Python which I know has tons of prerequisites as well).
Is there any way I can install all those prerequisites in once?
http://www.ibm.com/developerworks/aix/library/au-aix-manage-ruby/
I managed to get this done a couple of years ago (ruby 2.0.0).
I installed by compiling it from source as I did not have root access and wanted to install it in an afs directory anyway.
Here is my SO question and the my answer to my own question:
How do I configure ruby to compile in 64 bit mode on AIX
Here are some notes I had on how to do this as well.
if I recall using /usr/bin/ksh93 provided a huge speedup, I for get the details as to why, but using the default ksh installed on our servers was painfully slow.
export LIBPATH=/usr/lib
export CONFIG_SHELL=/usr/bin/ksh93
export OBJECT_MODE=64
./configure --enable-shared --enable-load-relative --disable-install-doc --prefix=your_install_path_here --exec-prefix=your_install_path_here/aix CC="gcc" CFLAGS="-maix64 -mminimal-toc" CXX="g++" CXXFLAGS="-maix64 -mminimal-toc" NM="nm -X64" AR="ar -X64" LDFLAGS="-maix64 -Wl,-bbigtoc" EXTLDFLAGS="-maix64 -Wl,-bbigtoc" DLDFLAGS="-shared -maix64 -Wl,-bbigtoc"
I would like to install a new version but this was really painful at the time.
Update
Another less painful way to use ruby on AIX is to install JRuby. I have done that as well, and make use of it for gui's via SWT. The biggest downside with JRuby is that it has to spin up a JVM, which takes some time. This is not a big deal for long running programs, but for short scripts it can be noticeable
I've done a fresh install of OS X Yosemite and Vagrant on my Mac some days ago. The problem is, that every time when I try to update all plugins or install a vagrant plugin (vagrant-cachier), I'll get the following error:
An error occurred while installing json (1.8.2), and Bundler cannot continue.
Make sure that `gem install json -v '1.8.2'` succeeds before bundling.
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
/opt/vagrant/embedded/bin/ruby extconf.rb
/opt/vagrant/embedded/bin/ruby: invalid option -H (-h will show valid options) (RuntimeError)
If I install a gem over the system's binary it works. So it seems to be a problem with the built-in vagrant binaries. I've also already installed the command line tools. My Vagrant Version is 1.7.2
I've already googled the problem for hours, but I didn't find this problem.
Did I forget anything or does anybody has a workaround for this problem?
Thanks!
Thanks for your help. I found the problem.
The problem was the path were Vagrant is installed. My SSD partition on OS X is called "Macintosh SSD" with a space in it.
I renamed it to "MacintoshSSD" and now it works fine.
The issue appears to be that the 'embedded' binary of ruby is not happy with some older code in the JSON gem. Or something... I literally know nothing about ruby other than that it is a programming language and I installed it to use compass. And now here it is again with Vagrant.
ANYWAY I moved the embedded ruby to the side, and copied OS X's built-in ruby into the vagrant embedded binaries folder.
Something like:
sudo mv /opt/vagrant/embedded/bin/ruby /opt/vagrant/embedded/bin/ruby.2.0.0.p598
sudo cp /usr/bin/ruby /opt/vagrant/embedded/bin/ruby.2.0.0.p481
sudo ln -s /opt/vagrant/embedded/bin/ruby.2.0.0.p481 /opt/vagrant/embedded/bin/ruby
sudo vagrant plugin install vagrant-vmware-fusion
Installing the 'vagrant-vmware-fusion' plugin. This can take a few minutes...
Installed the plugin 'vagrant-vmware-fusion (3.2.1)'!
Yay.
Straight from HashiCorp... here is the troubleshooting checklist:
Hey there,
I am really sorry you are having problems installing that Vagrant plugin. We are aware of these issues, but we have not been able to narrow it down to a specific cause because it only affects a small subset of machines and we have not identified a common denominator yet.
First, please do not try and install the plugin using sudo. This can tamper with the permissions of other Vagrant plugins and cause Vagrant to error.
Second, please ensure you have the XCode Command Line Tools installed. You can install them by running:
sudo xcode-select --install
and following the on-screen prompt.
After completing those steps, many users have found success by doing the following:
Completely uninstall Vagrant
Removing the /opt/vagrant and /Applications/vagrant directories.
Remove Vagrant's storage directory (~/.vagrant.d). Warning: If you
have installed other Vagrant plugins or Vagrant plugin licenses,
they will be removed!
Reinstall Vagrant from the official Vagrant installers:
https://www.vagrantup.com/downloads.html
Install the plugin
Additionally, please ensure the following:
If there is a special character anywhere in Vagrant's path, you must
choose a different directory. This includes spaces (like in a
username or folder name) and parenthesis (like C:/Program Files
(x86)). Unfortunately there is a bug in the language in which Vagrant
is written that prohibits compiling native extensions under these
circumstances.
If you are using a Mac, please make sure you have accepted the XCode
license agreement. In some situations, native extensions will fail to
compile because XCode is prohibiting the installation due to an
unaccepted license agreement. To accept the license agreement, simply
open XCode - you will be prompted if you need to accept the
agreement.
If the problem persists after taking these steps, please provide the output of the plugin installation's debug logs.
Please let me know if you have any questions.
Best,
Seth
When I run rvm install ruby-1.9.3, I get this error message when configuring
Error running ' ./configure --prefix=/Users/robbor911/.rvm/rubies/ruby-1.9.3-p125 --enable-shared --disable-install-doc --with-libyaml --with-opt-dir=/Users/robbor911/.rvm/usr ', please read /Users/robbor911/.rvm/log/ruby-1.9.3-p125/configure.log
There has been an error while running configure. Halting the installation.
All posts on this issue so far tell users to download XCode and install it, but I have it installed-- it even runs successfully.
From what I've gather, my problem has something to do with the terminal unable to locate the compiler's necessary for the download.
I even managed to locate the compilers at Xcode/Contents/Developer/usr/bin and Xode/Contents/Developer/usr/llvm-gcc-4.2/bin
Does anyone know why, when I installed XCode, my compilers weren't set up properly or how I can manually correct this issue?
I just ran across this issue the other day. The way I was able to get it running:
1) I downloaded and installed this package from Github.
2) ran rvm get head && rvm reload && rvm reinstall 1.9.3
Worked for me. Running OS Lion 10.7
Xcode 4.3 no longer installs the command-line tools by default. You can install them from the Downloads pane in Xcode's preferences.
I have been trying to install the Ruby PG gem, but kept getting the "Failed to build gem native extension." error.
After sifting through a lot of google results, I tried nearly every recommendation I came across, all without luck. However, I believe I've tracked down the source of the problem ... Homebrew.
Homebrew installed PostgreSQL 9.0.4, but only with the 32-bit libraries. As I am running Snow Leopard (10.6.8) with XCode 3.26, I need the 64-bit libraries in order to compile everything without library mismatch errors. But I cannot seem to find out how to force Homebrew to install them, even with ARCHFLAGS and ENV set to "-arch x86_64".
Suggestions, please :)
p.s. I found out that I only had 32-bit libraries installed by running:
file /usr/local/Cellar/postgresql/9.0.4/lib/libpq.5.3.dylib
which returned:
/usr/local/Cellar/postgresql/9.0.4/lib/libpq.5.3.dylib: Mach-O dynamically linked shared library i386
Update: re-installed Homebrew, which installed postgresql/9.1.1 and 64-bit shared libraries.
But another problem emerged, while installing the PG gem. For some reason it was looking for ginstall in /opt/local/bin. As I had removed MacPorts, that directory was also removed. I did find this solution:
mkdir -p /opt/local/bin/
sudo ln -s /usr/bin/install /opt/local/bin/ginstall
And now everything seems to be working ....
So it looks like my first install, using Homebrew, must have been done with regular Leopard.
Removing the Homebrew "Cell" directory and all of its contents, running the install script again, then doing "brew install" and "brew update" with all needed packages, got me the latest version of PostgreSQL, with 64-bit developer library.
And creating the above symbolic link fixed any left over errors from the MacPorts removal.
Now all is well :)
Can you please tell me how can I install scons on MacOSX?
I don't see a mac specified download from http://www.scons.org/
Thank you.
An alternative to MacPorts would be to use HomeBrew, where you'd just to
brew install scons
Download the tarball and then refer to the first chapter of the user guide, Building and Installing SCons. In short:
# cd scons-1.2.0
# python setup.py install
Install MacPorts, then at the Terminal (Applications > Utilities > Terminal.app), type:
sudo port install scons
This command will automatically download and install scons for you. MacPorts requires that you have the developer tools installed, so if you don't, you will need to download and install the Xcode 3 DVD.
NOTE 1: Xcode 2.5 is the last version of Xcode that will work on Mac OS X Tiger.
NOTE 2: This may seem awfully painful if you don't already have MacPorts installed. However, you really should go this route, as MacPorts makes it easy to update installed software, it automatically manages dependencies between software, and it makes it easier to install other packages in the future.
If you have the Python setuptools, the following will install scons-1.2.0 from sourceforge:
easy_install scons
But bear in mind the issues people raise with setuptools.
Also, keep in mind this question and the answers about virtualenv and pip for isolating Python environments.
There is also a GUI installer for SCons on Mac OS X that I wrote available for download here:
https://github.com/rviney/scons-mac-installer
Since version 2.3.0 SCons should work without installing:
# get the source and switch to stable 2.3.0 version
hg clone https://bitbucket.org/scons/scons/ -r 2.3.0
# make sure to use Python 2 for now
python scons/src/scripts/scons.py
When running 2.3.0 from source, the SCons.__version__ is not set correctly, so EnsureSConsVersion() will likely to fail if that's ok for you.
pull down SCons source and put it in /Library/Python/X.X/. Make sure you have the dir structure like this: /Library/Python/X.X/SCons/init.py
remember, import searches for modules, and /Library/Python/XXX is by default in the search path.