Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uninitialized constant #5

Open
mvexel opened this issue Jul 6, 2014 · 8 comments
Open

Uninitialized constant #5

mvexel opened this issue Jul 6, 2014 · 8 comments

Comments

@mvexel
Copy link
Contributor

mvexel commented Jul 6, 2014

calling geotag with no args:

/Users/martijnv/.rvm/gems/ruby-2.1.2/gems/geokit-1.8.5/lib/geokit/geocoders.rb:44:in `<module:Geocoders>': uninitialized constant Geokit::Geocoders::OpenSSL (NameError)

This is on OSX 10.9 with homebrew and rvm, using ruby 2.1.2.

@craigtaverner
Copy link
Contributor

I have geokit 1.8.4, and you have 1.8.5. Perhaps there is a new bug there?

@mvexel
Copy link
Contributor Author

mvexel commented Jul 6, 2014

gem list shows this.
I installed using gem install gpx2exif so bundle install would not be required? (Sorry my knowledge of Ruby dependency management / packaging is limited.)

@mvexel
Copy link
Contributor Author

mvexel commented Jul 6, 2014

Tried reinstalling ruby pointing to the homebrew-installed OpenSSL: rvm reinstall 2.1.2 --with-openssl-dir=/usr/local/Cellar/openssl/1.0.1h/ and reinstalling the geokit and gpx2exif gems afterwards, but that gives the same error. Next up is cloning the repo and installing from source.

@craigtaverner
Copy link
Contributor

Sorry I commented about bundle install too fast, then deleted my comment and put in a more reasonable one about the version of geokit. But seems you read and responded to my first comment anyway.

But my second comment about geokit versions seems correct. I've just upgraded to geokit 1.8.5 and also get the problem you see. Downgrading to geokit 1.8.4 should fix the problem.

@mvexel
Copy link
Contributor Author

mvexel commented Jul 6, 2014

Thanks @craigtaverner - let me try that. Is this known on the geokit side of things or do I need to file a bug?

@mvexel
Copy link
Contributor Author

mvexel commented Jul 6, 2014

That did the trick. So I guess gpx2exif should require geokit 1.8.4 at least until this gets fixed.

@craigtaverner
Copy link
Contributor

I don't know if it's known. I have not spent time looking at geokit much. Probably good to file a bug. Also I noticed that you installed gpx2exif from rubygems, but that get's you version 0.3.1. For the geotagging stuff I blogged about you need 0.3.6 or later. Until akwiatkowski merges my code, you need to get that from my fork.

git clone https://github.com/craigtaverner/gpx2exif
cd gpx2exif
bundle install
rake build
gem install pkg/gpx2exif-0.3.8.gem

mvexel added a commit to mvexel/gpx2exif that referenced this issue Jul 6, 2014
@craigtaverner
Copy link
Contributor

I edited the Gemfile on my fork to explicitly require geokit 1.8.4 until that bug is resolved.

akwiatkowski added a commit that referenced this issue Aug 19, 2014
requiring geokit 1.8.4 because of #5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants