Installing error

Issue #27 new
Former user created an issue

Hi, The python setup.py install is giving me an error:

"testing git availability ... fatal: not a git repository (or any of the parent directories): .git running install running bdist_egg running egg_info creating lsa.egg-info writing requirements to lsa.egg-info/requires.txt writing lsa.egg-info/PKG-INFO writing top-level names to lsa.egg-info/top_level.txt writing dependency_links to lsa.egg-info/dependency_links.txt writing entry points to lsa.egg-info/entry_points.txt writing manifest file 'lsa.egg-info/SOURCES.txt' reading manifest file 'lsa.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'README.txt' writing manifest file 'lsa.egg-info/SOURCES.txt' installing library code to build/bdist.macosx-10.7-x86_64/egg running install_lib running build_py creating build creating build/lib.macosx-10.7-x86_64-2.7 creating build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/init.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/compcore.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsalib.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsaio.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/laio.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsa_version.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsa_query.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/la_query.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/la_compute.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/ssa.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/par_ana.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/ptheo.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/to_trend.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsa_sim.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/fix_qv.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/check_data.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsa_infer.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/vtrend.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsalibx.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lalib.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lsa_compute.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/lla_compute.py -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/compcore.cpp -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/compcore.hpp -> build/lib.macosx-10.7-x86_64-2.7/lsa copying lsa/compcore_wrap.cpp -> build/lib.macosx-10.7-x86_64-2.7/lsa running build_ext building 'lsa._compcore' extension creating build/temp.macosx-10.7-x86_64-2.7 creating build/temp.macosx-10.7-x86_64-2.7/lsa gcc -fno-strict-aliasing -I/Users/DanCakeRosado/miniconda2/envs/py27/include -arch x86_64 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/DanCakeRosado/miniconda2/envs/py27/include/python2.7 -c lsa/compcore_wrap.cpp -o build/temp.macosx-10.7-x86_64-2.7/lsa/compcore_wrap.o warning: include path for stdlibc++ headers not found; pass '-std=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found] lsa/compcore_wrap.cpp:2376:23: warning: explicitly assigning value of variable of type 'int' to itself [-Wself-assign] res = SWIG_AddCast(res); ~ ^ ~ lsa/compcore_wrap.cpp:2379:23: warning: explicitly assigning value of variable of type 'int' to itself [-Wself-assign] res = SWIG_AddCast(res);
~ ^ ~ lsa/compcore_wrap.cpp:2901:9: warning: variable 'res' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized] if (PyType_Ready(tp) < 0) ^~~~~~ lsa/compcore_wrap.cpp:2925:10: note: uninitialized use occurs here return res; ^ lsa/compcore_wrap.cpp:2901:5: note: remove the 'if' if its condition is always false if (PyType_Ready(tp) < 0) ^~~~~~~ lsa/compcore_wrap.cpp:2882:10: note: initialize the variable 'res' to silence this warning int res; ^ = 0 lsa/compcore_wrap.cpp:3000:10: fatal error: 'stdexcept' file not found #include <stdexcept> ^~~~~ 4 warnings and 1 error generated. error: command 'gcc' failed with exit status 1"

Can you help? Thank you

Comments (0)

  1. Log in to comment