Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Norbert Melzer Newsgroups: comp.lang.ruby Subject: Re: massive_record gem issue Date: 3 Aug 2014 10:11:54 GMT Lines: 17 Message-ID: References: <3d0d0a12-ccc7-400e-a3bc-3e46cfc1d521@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net hXnjft22wkeCj54zMRsKgQxyzSo/tJs2hBXcryf/3B+KViNcbq Cancel-Lock: sha1:nSZPdZgggzYdRz859KNCygqQyDY= User-Agent: PhoNews/1.2.1 (Android) In-Reply-To: <3d0d0a12-ccc7-400e-a3bc-3e46cfc1d521@googlegroups.com> Xref: csiph.com comp.lang.ruby:7010 Am 03.08.14 11:05, schrieb Melb: > /usr/bin/ruby1.9.1 extconf.rb From massive_records readme: | Installation | | First of all: Please make sure you are using Ruby 1.9.2. For now, we are only | ensuring that Massive Record works on that Ruby version, and we know it has some | problems with 1.8.7. Please try again with that Version. Also you should beware of the fact that the last release is about 2 and a half year old, also development activity on hiring dropped drastically about half a year after that release.