One more thought ... would it help to delete the app and then regenerate it with ruby 1.9.2 to start with? For the record, I'm using Ramaze and Sequel here, not Rails.
Scott On Mon, Dec 13, 2010 at 10:49 AM, Scott LaBounty <[email protected]>wrote: > OK, when I changed something and did a new push, I get ... > > << > -----> Installing gem ruby-pg from http://rubygems.org > Building native extensions. This could take a while... > ERROR: Error installing ruby-pg: > ERROR: Failed to build gem native extension. > > /usr/ruby1.9.2/bin/ruby extconf.rb > *** extconf.rb failed *** > Could not create Makefile due to some reason, probably lack of > necessary libraries and/or headers. Check the mkmf.log file for > more > details. You may need configuration options. > > Provided configuration options: > --with-opt-dir > --without-opt-dir > --with-opt-include > --without-opt-include=${opt-dir}/include > --with-opt-lib > --without-opt-lib=${opt-dir}/lib > --with-make-prog > --without-make-prog > --srcdir=. > --curdir > --ruby=/usr/ruby1.9.2/bin/ruby > extconf.rb:4:in `<main>': uninitialized constant Object::PLATFORM > (NameError) > > > Gem files will remain installed in > /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28 for inspection. > Results logged to > /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28/ext/gem_make.out > ! Heroku push rejected, failed to install gem > >> > > It looks like the ruby-pg gem won't build with 1.9.2? > > Scott > > > On Mon, Dec 13, 2010 at 9:59 AM, Scott LaBounty <[email protected]>wrote: > >> All, >> >> I was getting the following error: >> >> << >> /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/model/init.rb:10: >> undefined method `require_relative' for main:Object (NoMethodError) >> from >> /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in >> `gem_original_require' >> from >> /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in >> `require' >> from >> /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/app.rb:13 >> from >> /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in >> `gem_original_require' >> from >> /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in >> `require' >> from config.ru:18 >> from /home/heroku_rack/heroku.ru:23 >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >> `instance_eval' >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >> `initialize' >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:63:in >> `new' >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:63:in >> `map' >> from /home/heroku_rack/heroku.ru:18 >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >> `instance_eval' >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >> `initialize' >> from /home/heroku_rack/heroku.ru:11:in `new' >> from /home/heroku_rack/heroku.ru:11 >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >> `instance_eval' >> from >> /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.gems/gems/rack-1.2.1/lib/rack/builder.rb:46:in >> `initialize' >> from /home/heroku_rack/heroku.ru:1:in `new' >> from /home/heroku_rack/heroku.ru:1 >> >> >> >> since "require_relative" is a 1.9.2 feature of ruby, I did a: >> >> heroku stack:migrate bamboo-mri-1.9.2 >> git push heroku master >> >> and I'm getting the same error. >> >> When I do a: >> >> heroku stack >> >> I see: >> >> aspen-mri-1.8.6 >> * bamboo-ree-1.8.7 >> bamboo-mri-1.9.1 (beta) >> bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git push) >> >> so I tried doing: >> >> touch README >> git push heroku master >> >> and the stack is still the same. What else do I need to do to change the >> stack? >> >> >> -- >> Scott >> http://steamcode.blogspot.com/ >> > > > > -- > Scott > http://steamcode.blogspot.com/ > -- Scott http://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
