Name conflict between Geod in GeographicLib and geod in proj-4.8.0.

  • Anonymous - 2013-10-19

    A name conflict seemed to occur when I installed geographiclib using homebrew in macosx. The following message says that it is the conflict between Geod in GeographicLib and geod in proj-4.8.0.

    $ brew install GeographicLib
    ==> Downloading
    Already downloaded: /Library/Caches/Homebrew/geographiclib-1.33.tar.gz
    ==> ./configure --prefix=/usr/local/Cellar/geographiclib/1.33
    ==> make install
    Warning: Could not link geographiclib. Unlinking...
    Error: The `brew link` step did not complete successfully
    The formula built, but is not symlinked into /usr/local
    You can try again using `brew link geographiclib'
    Possible conflicting files are:
    /usr/local/bin/Geod -> /usr/local/Cellar/proj/4.8.0/bin/geod
  • Charles Karney

    Charles Karney - 2013-10-19

    I'm not sure why there exists the link from /usr/local/bin/Geod to the
    proj.4 utility geod. For now I recommend that you follow the advice you
    are given and run `brew link geographiclib'. GeographicLib's utility
    Geod is now officially called GeodSolve (as of version 1.30) and the
    name Geod is only included for backwards compatibility. So after
    installing GeographicLib, you can reestablish the proj.4 link without
    any loss of functionality.

    Finally, note that the proj.4 utility geod has several defects in
    versions 4.8.0 and earlier. In the next version of proj.4 (version
    4.9.0, I believe), the geod utility will be replaced by one based on the
    algorithms used by GeographicLib (however the user interface will remain
    the proj.4 one).

  • Anonymous - 2013-10-27

    Thank you for your advice.

    I am considering removing geographiclib's backwards-compatible Geod if it would not cause trouble, because MacOSX is basically case-insensitive and the coexistence of geod and Geod is now allowed.



Cancel  Add attachments

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks