Skip to content

Instantly share code, notes, and snippets.

@cfriedline
Created August 28, 2014 05:17
Show Gist options
  • Save cfriedline/1086653f09110260fa25 to your computer and use it in GitHub Desktop.
Save cfriedline/1086653f09110260fa25 to your computer and use it in GitHub Desktop.
revbayes compile fail
[ 99%] Building CXX object ui/CMakeFiles/rb-ui.dir/Users/chris/src/revbayes/src/ui/RbClient.cpp.o
In file included from /Users/chris/src/revbayes/src/ui/RbClient.cpp:1:
In file included from /Users/chris/src/revbayes/projects/cmake/../../src/ui/RbClient.h:8:
In file included from /Users/chris/src/revbayes/projects/cmake/../../src/libs/lineedit/EditorMachineObserver.h:11:
In file included from /Users/chris/src/revbayes/projects/cmake/../../src/libs/lineedit/EditorState.h:8:
/Users/chris/src/revbayes/projects/cmake/../../src/libs/lineedit/lineeditUtils.h:35:20: warning: implicit conversion
from 'const size_type' (aka 'const unsigned long') to 'int' changes value from 18446744073709551615 to -1
[-Wconstant-conversion]
int rPos = std::string::npos, _rPos, tmpInt;
~~~~ ^~~~~~~~~~~~~~~~~
In file included from /Users/chris/src/revbayes/src/ui/RbClient.cpp:4:
/Users/chris/src/revbayes/projects/cmake/../../src/ui/WorkspaceUtils.h:121:82: error: no member named
'getNewTypeObject' in 'RevLanguage::Workspace'
RevLanguage::RevObject *type = RevLanguage::Workspace::globalWorkspace().getNewTypeObject(typeName);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
1 warning and 1 error generated.
make[2]: *** [ui/CMakeFiles/rb-ui.dir/Users/chris/src/revbayes/src/ui/RbClient.cpp.o] Error 1
make[1]: *** [ui/CMakeFiles/rb-ui.dir/all] Error 2
make: *** [all] Error 2
@hoehna
Copy link

hoehna commented Aug 28, 2014

Oh, well, that happens because we are still on the development branch and it seems that make was done from the Master branch. Could you change? We will push to Master after the workshop.

Sebastian

@mlandis
Copy link

mlandis commented Aug 28, 2014

How about we merge development into master now, since development is stable and compiles, then merge again and tag that commit on master as release after the workshop?

Michael

@cfriedline
Copy link
Author

Makes sense. I'll compile from development. Thanks!

@cfriedline
Copy link
Author

Compiling from development was fine. I also had to do this:

ln -s ../../boost_1_55_0/stage/lib/*.dylib .

into the projects/cmake directory

because of:

$ otool -L rb
rb:
libboost_filesystem.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_regex.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_program_options.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_system.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_thread.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_context.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_signals.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_date_time.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_iostreams.dylib (compatibility version 0.0.0, current version 0.0.0)
libboost_serialization.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 60.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)

And I just noticed that similar instructions are on the NESCent course wiki. Doh. ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment