I'm working on my Github Pages site, so need to build it on my local machine. Following their instructions, I have set it up using bundler. However bundler appears to break the Jekyll build.
If I run jekyll new NewSite it creates a new site that can be built using jekyll serve. As soon as I run bundle install, or bundle update, however, Jekyll refuses to run, giving the below error on the "generating" step.
jekyll 3.0.5 | Error: No such file or directory - git remote --verbose
It will then give that same error every time either bundle exec jekyll serve or jekyll serve are called. Further investigation has found that the error goes away if the gemfile file is deleted.
What have I misconfigured?
Update:
I've added a stack trace as requested
I realised it was the gemfile itself that was causing the issue, not the gemfile.lock
Problem turned out to have nothing to do with Windows, so removed references to it
Stack trace:
C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:32
:in ``': No such file or directory - git remote --verbose (Errno::ENOENT)
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:32:in `git_remote_url'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:39:in `nwo_from_git_origin_remote'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:65:in `nwo'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:8:in `generate'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:154:in `block in generate'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:153:in `each'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:153:in `generate'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:58:in `process'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/command.rb:28:in `process_site'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/commands/build.rb:60:in `build'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/commands/build.rb:35:in `process'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/commands/serve.rb:26:in `block (2 levels) in init_with_program'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `call'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/bin/jekyll:17:in `<top (required)>'
from C:/Ruby22/bin/jekyll:23:in `load'
from C:/Ruby22/bin/jekyll:23:in `<main>'
My Gemfile:
source 'https://rubygems.org'
gem 'github-pages', group: :jekyll_plugins
gem 'safe_yaml', '~> 1.0.4'
gem 'wdm', '~> 0.1.0' if Gem.win_platform?
Ruby version: 2.2.4 32 bit
Bundler version: 1.12.3
Jekyll Version: 3.0.5
This is jekyll-github-metadata gem which is bugging when trying to run a git remote --verbose command on your system (code).
You can try to set a _config.yml variable (documentation) :
repository: username/repo-name
Related
I am using Arctic Fox 2020.3.1 (ARM version- designed for Apple silicon), on Macbook Air M1 2020 model, running flutter project. I am successfully able to run on Android emulator, but when i try to run on attached iOS device or iOS simulator "pod install" command fails and build failed. But when i open my terminal on rosetta 2 and try "pod install" manually it install all pods, and after that i am able to run the build from XCODE but not from Android Studio, so my question is: Is terminal inside Android Studio runs on Apple (not on rosetta 2) that's why it fails.
Note: I have changed the configuration of terminal to run it forcefully on rosetta 2.
This happens when i try to run for ios from studio
The plugins `flutter_full_pdf_viewer, flutter_webview_plugin, onesignal_flutter` use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.
Launching lib/main.dart on Lakhwinder’s iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: E942NB2Q9L
Running pod install...
CocoaPods' output:
↳
CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
Error output from CocoaPods:
↳
WARNING: CocoaPods requires your terminal to be using UTF-8 encoding.
Consider adding the following to ~/.profile:
export LANG=en_US.UTF-8
/opt/homebrew/Cellar/ruby/3.0.2/lib/ruby/3.0.0/unicode_normalize/normalize.rb:141:in `normalize': Unicode Normalization not appropriate for ASCII-8BIT (Encoding::CompatibilityError)
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `unicode_normalize'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `installation_root'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:226:in `podfile_path'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/user_interface/error_report.rb:105:in `markdown_podfile'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/user_interface/error_report.rb:30:in `report'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:66:in `report_error'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:396:in `handle_exception'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:337:in `rescue in run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:324:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `load'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `<main>'
/opt/homebrew/Cellar/ruby/3.0.2/lib/ruby/3.0.0/unicode_normalize/normalize.rb:141:in `normalize': Unicode Normalization not appropriate for ASCII-8BIT (Encoding::CompatibilityError)
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `unicode_normalize'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `installation_root'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:226:in `podfile_path'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:205:in `podfile'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:160:in `verify_podfile_exists!'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command/install.rb:46:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `load'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `<main>'
Exception: Error running pod install
open Terminal type open ~/.zshrc (or .profile if you don't use zsh)
It seems that LANG="en_US.UTF-8" alone isn't enough, you have to set
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
export LC_ALL=en_US.UTF-8
save the file
go back to Terminal
type source ~/.zshrc
type locale
You can now safely run pod update or pod install
You may have to install ffi. Run sudo gem install ffi then normal flutter run should work as expected.
When I run flutter doctor an error occured asking to install cocoapods. Then I tried to install cocoapods and the blow error was given. Please help me to solve this error.
thejanisaranaguptha#Thejanis-MacBook-Pro ~ % sudo gem install cocoapods
Building native extensions. This could take a while...
ERROR: Error installing cocoapods:
ERROR: Failed to build gem native extension.
current directory: /Library/Ruby/Gems/2.6.0/gems/ffi-1.14.2/ext/ffi_c
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby -I /Library/Ruby/Site/2.6.0 -r ./siteconf20210306-2856-1tbjsvn.rb extconf.rb
checking for ffi.h... *** 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.
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:467:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:585:in `block in try_compile'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:534:in `with_werror'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:585:in `try_compile'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:1109:in `block in have_header'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:959:in `block in checking_for'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:361:in `block (2 levels) in postpone'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:331:in `open'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:361:in `block in postpone'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:331:in `open'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:357:in `postpone'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:958:in `checking_for'
from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/mkmf.rb:1108:in `have_header'
from extconf.rb:10:in `system_libffi_usable?'
from extconf.rb:42:in `<main>'
To see why this extension failed to compile, please check the mkmf.log which can be found here:
/Library/Ruby/Gems/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.14.2/mkmf.log
extconf failed, exit code 1
Gem files will remain installed in /Library/Ruby/Gems/2.6.0/gems/ffi-1.14.2 for inspection.
Results logged to /Library/Ruby/Gems/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.14.2/gem_make.out
if you have Homebrew installed,Try this
brew install cocoapods
reference
When I clone the project from https://github.com/daattali/beautiful-jekyll.git on my computer, I use jekyll serve to start the project, but it will some error, what should I do if I want to Local development using jekyll?
the error is:
WARN: Unresolved specs during Gem::Specification.reset:
jekyll-watch (~> 1.1)
rouge (< 3, >= 1.7)
rb-fsevent (>= 0.9.4, ~> 0.9)
rb-inotify (>= 0.9.7, ~> 0.9)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/runtime.rb:313:in `check_for_activated_spec!': You have already activated public_suffix 3.0.1, but your Gemfile requires public_suffix 2.0.5. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/runtime.rb:31:in `block in setup'
from C:/Ruby24-x64/lib/ruby/2.4.0/forwardable.rb:229:in `each'
from C:/Ruby24-x64/lib/ruby/2.4.0/forwardable.rb:229:in `each'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/runtime.rb:26:in `map'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-`enter code here`1.16.0/lib/bundler/runtime.rb:26:in `setup'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler.rb:107:in `setup'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-3.6.2/lib/jekyll/plugin_manager.rb:50:in `require_from_bundler'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-3.6.2/exe/jekyll:11:in `<top (required)>'
from C:/Ruby24-x64/bin/jekyll:23:in `load'
from C:/Ruby24-x64/bin/jekyll:23:in `<main>'
I have solved my question.
First: you should add the code to your Gemfile file.
the code is
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
Then: you use bundle exec jekyll serve to start. After that you can use local development.
I pulled the latest source from github.
I'm trying to build:
stephan#E6520:~/dev/ember.js$ rake
rake aborted!
no such file to load -- net/github-upload
the trace:
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/rake_module.rb:25:in `load'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/rake_module.rb:25:in `load_rakefile'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:501:in `raw_load_rakefile'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:82:in `block in load_rakefile'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:81:in `load_rakefile'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:65:in `block in run'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
.rvm/gems/ruby-1.9.2-p180/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
.rvm/gems/ruby-1.9.2-p180/bin/rake:19:in `load'
.rvm/gems/ruby-1.9.2-p180/bin/rake:19:in `<main>'
github upload seemed to be missing so
I installed github-upload using the following:
rvm install github-upload --with-openssl-dir=$rvm_path/usr
But i keep having the same error.
I had same issue, try to execute "bundle install" and then "rake" again (hope I remember correctly)
I removed github-upload requirement in the RakeFile.
Then I got other 'errors' i could solve again. By running the suggested bundle install
And now emberjs Builds.
At my wits end with this!
My current set up is:
- Ruby 1.9.2
- Rails 3.0.1
- pg (0.9.0)
My $PATH right now looks like this:
/Users/fjones/.rvm/gems/ruby-1.9.2-p0/bin:/Users/fjones/.rvm/gems/ruby-1.9.2-p0#global/bin:/Users/fjones/.rvm/rubies/ruby-1.9.2-p0/bin:/Users/fjones/.rvm/bin:ARCHFLAGS=-arch
x86_64:/opt/local/bin:/opt/local/sbin:/opt/local/lib/postgresql84/bin:/Library/Glassfish/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
Anytime I attempt to do a "bundle install" from Netbeans 6.9.1 I get the following exception.
Installing pg (0.9.0) with native
extensions
/Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:483:in
`rescue in block in build_extensions':
ERROR: Failed to build gem native
extension.
(Gem::Installer::ExtensionBuildError)
/Users/fjones/.rvm/rubies/ruby-1.9.2-p0/bin/ruby
extconf.rb checking for pg_config...
no
=========== WARNING ===========
You are building this extension on OS X without setting the
ARCHFLAGS environment variable, and
pg_config wasn't found in your
PATH. If you are seeing this message,
that means that the build will
probably fail.
If it does, you can correct this by
either including the path to
'pg_config' in your PATH or setting
the environment variable ARCHFLAGS
to '-arch ' before building.
For example: (in bash) $ export
PATH=/opt/local/lib/postgresql84/bin:$PATH
$ export ARCHFLAGS='-arch x86_64' (in tcsh) % set path = (
/opt/local/lib/postgresql84/bin $PATH
)
% setenv ARCHFLAGS '-arch x86_64'
Then try building again.
===================================
MacOS X build: fixing architecture
flags: checking for libpq-fe.h... no
Can't find the 'libpq-fe.h header
* 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=/Users/fjones/.rvm/rubies/ruby-1.9.2-p0/bin/ruby
--with-pg
--without-pg
--with-pg-config
--without-pg-config
--with-pg-dir
--without-pg-dir
--with-pg-include
--without-pg-include=${pg-dir}/include
--with-pg-lib
--without-pg-lib=${pg-dir}/lib
--enable-static-build
--disable-static-build
Gem files will remain installed in
/Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/pg-0.9.0
for inspection. Results logged to
/Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/pg-0.9.0/ext/gem_make.out
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:486:in
block in build_extensions'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:446:in
each'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:446:in
build_extensions'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:198:in
install'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/source.rb:100:in
install'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/installer.rb:55:in
block in run'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/spec_set.rb:12:in
block in each'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/spec_set.rb:12:in
each'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/spec_set.rb:12:in
each'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/installer.rb:44:in
run'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/installer.rb:8:in
install'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/cli.rb:221:in
install'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/vendor/thor/task.rb:22:in
run'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/vendor/thor/invocation.rb:118:in
invoke_task'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/vendor/thor.rb:246:in
dispatch'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/vendor/thor/base.rb:389:in
start'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/bin/bundle:13:in
<top (required)>'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/bin/bundle:19:in
load'
from /Users/fjones/.rvm/rubies/ruby-1.9.2-p0/bin/bundle:19:in
`'
Seems like you need to install the development version of libpq (headers and libraries). Unfortunately I have no idea what exactly should be done on OS X.
ANSWER:
So this is really a problem with Netbeans 6.9.1 not assigning the correct path info for Ruby 1.9.2 gems. The solution:
Go to Tools > Ruby Platforms
Select Ruby 1.9.2-p0 in the Platforms listbox
Update "Gem Home" and "Gem Path" based on what those paths should be (run "gem env" from Terminal to get that info)
This will actually fix a number of things in addition to being able to run "bundle install" with the pg gem. In addition you'll be able to install the fast debugger for 1.9.2 and manage your other gems from within netbeans.