Install fail - Ubuntu 13.04, Anaconda 1.8

109 views
Skip to first unread message

Michael Sarahan

unread,
Mar 2, 2014, 1:48:47 PM3/2/14
to xdr...@googlegroups.com
Hello,

Not sure whether this is better posted here or on Anaconda's mailing list.  Let me know if I should post over there instead.

I have just tried to do a pip install xdress on Ubuntu 13.04 (x64).  It seems to have an issue with Anaconda.  If I take Anaconda off of my PATH, pip installs xdress successfully.  It looks like it's using LLVM configuration from Anaconda's build of LLVM/clang, which doesn't necessarily match Ubuntu's configuration. (Just a wild guess - I'm not familiar with this stuff.)

Output from pip with Anaconda below.  Any ideas on a fix or workaround?

Thanks,
Michael

Downloading/unpacking xdress
  Downloading xdress-0.4.tar.gz (163kB): 163kB downloaded
  Running setup.py (path:/tmp/pip_build_msarahan/xdress/setup.py) egg_info for package xdress
   
    XXXXXXX       XXXXXXXDDDDDDDDDDDDD
    X:::::X       X:::::XD::::::::::::DDD
    X:::::X       X:::::XD:::::::::::::::DD
    X::::::X     X::::::XDDD:::::DDDDD:::::D
    XXX:::::X   X:::::XXX  D:::::D    D:::::D
       X:::::X X:::::X     D:::::D     D:::::D
        X:::::X:::::X      D:::::D     D:::::D
         X:::::::::X       D:::::D     D:::::D
         X:::::::::X       D:::::D     D:::::D
        X:::::X:::::X      D:::::D     D:::::D
       X:::::X X:::::X     D:::::D     D:::::D
    XXX:::::X   X:::::XXX  D:::::D    D:::::D
    X::::::X     X::::::XDDD:::::DDDDD:::::D
    X:::::X       X:::::XD:::::::::::::::DD
    X:::::X       X:::::XD::::::::::::DDD
    XXXXXXX       XXXXXXXDDDDDDDDDDDDD
   
    using llvm-config from /home/msarahan/anaconda/bin/llvm-config
   
    warning: no files found matching 'xdress/*.cpp'
Installing collected packages: xdress
  Running setup.py install for xdress
   
    XXXXXXX       XXXXXXXDDDDDDDDDDDDD
    X:::::X       X:::::XD::::::::::::DDD
    X:::::X       X:::::XD:::::::::::::::DD
    X::::::X     X::::::XDDD:::::DDDDD:::::D
    XXX:::::X   X:::::XXX  D:::::D    D:::::D
       X:::::X X:::::X     D:::::D     D:::::D
        X:::::X:::::X      D:::::D     D:::::D
         X:::::::::X       D:::::D     D:::::D
         X:::::::::X       D:::::D     D:::::D
        X:::::X:::::X      D:::::D     D:::::D
       X:::::X X:::::X     D:::::D     D:::::D
    XXX:::::X   X:::::XXX  D:::::D    D:::::D
    X::::::X     X::::::XDDD:::::DDDDD:::::D
    X:::::X       X:::::XD:::::::::::::::DD
    X:::::X       X:::::XD::::::::::::DDD
    XXXXXXX       XXXXXXXDDDDDDDDDDDDD
   
    using llvm-config from /home/msarahan/anaconda/bin/llvm-config
    building 'xdress.clang.libclang' extension
    g++ -pthread -shared -L/home/msarahan/anaconda/lib -lclangTooling -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangStaticAnalyzerFrontend -lclangStaticAnalyzerCheckers -lclangStaticAnalyzerCore -lclangAnalysis -lclangARCMigrate -lclangEdit -lclangRewriteCore -lclangAST -lclangLex -lclangBasic -lpython2.7 -o build/lib.linux-x86_64-2.7/xdress/clang/libclang.so -L/home/msarahan/anaconda/lib -lz -lpthread -lrt -ldl -lm -lLLVMInstrumentation -lLLVMArchive -lLLVMLinker -lLLVMIRReader -lLLVMBitReader -lLLVMAsmParser -lLLVMDebugInfo -lLLVMOption -lLLVMipo -lLLVMVectorize -lLLVMBitWriter -lLLVMTableGen -lLLVMSystemZCodeGen -lLLVMSystemZAsmParser -lLLVMSystemZDesc -lLLVMSystemZInfo -lLLVMSystemZAsmPrinter -lLLVMHexagonCodeGen -lLLVMHexagonAsmPrinter -lLLVMHexagonDesc -lLLVMHexagonInfo -lLLVMNVPTXCodeGen -lLLVMNVPTXDesc -lLLVMNVPTXInfo -lLLVMNVPTXAsmPrinter -lLLVMMBlazeDisassembler -lLLVMMBlazeCodeGen -lLLVMMBlazeDesc -lLLVMMBlazeAsmPrinter -lLLVMMBlazeAsmParser -lLLVMMBlazeInfo -lLLVMCppBackendCodeGen -lLLVMCppBackendInfo -lLLVMMSP430CodeGen -lLLVMMSP430Desc -lLLVMMSP430Info -lLLVMMSP430AsmPrinter -lLLVMXCoreDisassembler -lLLVMXCoreCodeGen -lLLVMXCoreDesc -lLLVMXCoreInfo -lLLVMXCoreAsmPrinter -lLLVMMipsDisassembler -lLLVMMipsCodeGen -lLLVMMipsAsmParser -lLLVMMipsDesc -lLLVMMipsInfo -lLLVMMipsAsmPrinter -lLLVMARMDisassembler -lLLVMARMCodeGen -lLLVMARMAsmParser -lLLVMARMDesc -lLLVMARMInfo -lLLVMARMAsmPrinter -lLLVMAArch64Disassembler -lLLVMAArch64CodeGen -lLLVMAArch64AsmParser -lLLVMAArch64Desc -lLLVMAArch64Info -lLLVMAArch64AsmPrinter -lLLVMAArch64Utils -lLLVMPowerPCCodeGen -lLLVMPowerPCDesc -lLLVMPowerPCAsmPrinter -lLLVMPowerPCAsmParser -lLLVMPowerPCInfo -lLLVMSparcCodeGen -lLLVMSparcDesc -lLLVMSparcInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInterpreter -lLLVMMCJIT -lLLVMJIT -lLLVMCodeGen -lLLVMObjCARCOpts -lLLVMScalarOpts -lLLVMInstCombine -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMRuntimeDyld -lLLVMExecutionEngine -lLLVMTarget -lLLVMMC -lLLVMObject -lLLVMCore -lLLVMSupport
    /usr/bin/ld: cannot find -lLLVMInstrumentation
    /usr/bin/ld: cannot find -lLLVMArchive
    /usr/bin/ld: cannot find -lLLVMLinker
    /usr/bin/ld: cannot find -lLLVMIRReader
    /usr/bin/ld: cannot find -lLLVMBitReader
    /usr/bin/ld: cannot find -lLLVMAsmParser
    /usr/bin/ld: cannot find -lLLVMDebugInfo
    /usr/bin/ld: cannot find -lLLVMOption
    /usr/bin/ld: cannot find -lLLVMipo
    /usr/bin/ld: cannot find -lLLVMVectorize
    /usr/bin/ld: cannot find -lLLVMBitWriter
    /usr/bin/ld: cannot find -lLLVMTableGen
    /usr/bin/ld: cannot find -lLLVMSystemZCodeGen
    /usr/bin/ld: cannot find -lLLVMSystemZAsmParser
    /usr/bin/ld: cannot find -lLLVMSystemZDesc
    /usr/bin/ld: cannot find -lLLVMSystemZInfo
    /usr/bin/ld: cannot find -lLLVMSystemZAsmPrinter
    /usr/bin/ld: cannot find -lLLVMHexagonCodeGen
    /usr/bin/ld: cannot find -lLLVMHexagonAsmPrinter
    /usr/bin/ld: cannot find -lLLVMHexagonDesc
    /usr/bin/ld: cannot find -lLLVMHexagonInfo
    /usr/bin/ld: cannot find -lLLVMNVPTXCodeGen
    /usr/bin/ld: cannot find -lLLVMNVPTXDesc
    /usr/bin/ld: cannot find -lLLVMNVPTXInfo
    /usr/bin/ld: cannot find -lLLVMNVPTXAsmPrinter
    /usr/bin/ld: cannot find -lLLVMMBlazeDisassembler
    /usr/bin/ld: cannot find -lLLVMMBlazeCodeGen
    /usr/bin/ld: cannot find -lLLVMMBlazeDesc
    /usr/bin/ld: cannot find -lLLVMMBlazeAsmPrinter
    /usr/bin/ld: cannot find -lLLVMMBlazeAsmParser
    /usr/bin/ld: cannot find -lLLVMMBlazeInfo
    /usr/bin/ld: cannot find -lLLVMCppBackendCodeGen
    /usr/bin/ld: cannot find -lLLVMCppBackendInfo
    /usr/bin/ld: cannot find -lLLVMMSP430CodeGen
    /usr/bin/ld: cannot find -lLLVMMSP430Desc
    /usr/bin/ld: cannot find -lLLVMMSP430Info
    /usr/bin/ld: cannot find -lLLVMMSP430AsmPrinter
    /usr/bin/ld: cannot find -lLLVMXCoreDisassembler
    /usr/bin/ld: cannot find -lLLVMXCoreCodeGen
    /usr/bin/ld: cannot find -lLLVMXCoreDesc
    /usr/bin/ld: cannot find -lLLVMXCoreInfo
    /usr/bin/ld: cannot find -lLLVMXCoreAsmPrinter
    /usr/bin/ld: cannot find -lLLVMMipsDisassembler
    /usr/bin/ld: cannot find -lLLVMMipsCodeGen
    /usr/bin/ld: cannot find -lLLVMMipsAsmParser
    /usr/bin/ld: cannot find -lLLVMMipsDesc
    /usr/bin/ld: cannot find -lLLVMMipsInfo
    /usr/bin/ld: cannot find -lLLVMMipsAsmPrinter
    /usr/bin/ld: cannot find -lLLVMARMDisassembler
    /usr/bin/ld: cannot find -lLLVMARMCodeGen
    /usr/bin/ld: cannot find -lLLVMARMAsmParser
    /usr/bin/ld: cannot find -lLLVMARMDesc
    /usr/bin/ld: cannot find -lLLVMARMInfo
    /usr/bin/ld: cannot find -lLLVMARMAsmPrinter
    /usr/bin/ld: cannot find -lLLVMAArch64Disassembler
    /usr/bin/ld: cannot find -lLLVMAArch64CodeGen
    /usr/bin/ld: cannot find -lLLVMAArch64AsmParser
    /usr/bin/ld: cannot find -lLLVMAArch64Desc
    /usr/bin/ld: cannot find -lLLVMAArch64Info
    /usr/bin/ld: cannot find -lLLVMAArch64AsmPrinter
    /usr/bin/ld: cannot find -lLLVMAArch64Utils
    /usr/bin/ld: cannot find -lLLVMPowerPCCodeGen
    /usr/bin/ld: cannot find -lLLVMPowerPCDesc
    /usr/bin/ld: cannot find -lLLVMPowerPCAsmPrinter
    /usr/bin/ld: cannot find -lLLVMPowerPCAsmParser
    /usr/bin/ld: cannot find -lLLVMPowerPCInfo
    /usr/bin/ld: cannot find -lLLVMSparcCodeGen
    /usr/bin/ld: cannot find -lLLVMSparcDesc
    /usr/bin/ld: cannot find -lLLVMSparcInfo
    /usr/bin/ld: cannot find -lLLVMX86Disassembler
    /usr/bin/ld: cannot find -lLLVMX86AsmParser
    /usr/bin/ld: cannot find -lLLVMX86CodeGen
    /usr/bin/ld: cannot find -lLLVMSelectionDAG
    /usr/bin/ld: cannot find -lLLVMAsmPrinter
    /usr/bin/ld: cannot find -lLLVMX86Desc
    /usr/bin/ld: cannot find -lLLVMX86Info
    /usr/bin/ld: cannot find -lLLVMX86AsmPrinter
    /usr/bin/ld: cannot find -lLLVMX86Utils
    /usr/bin/ld: cannot find -lLLVMMCDisassembler
    /usr/bin/ld: cannot find -lLLVMMCParser
    /usr/bin/ld: cannot find -lLLVMInterpreter
    /usr/bin/ld: cannot find -lLLVMMCJIT
    /usr/bin/ld: cannot find -lLLVMJIT
    /usr/bin/ld: cannot find -lLLVMCodeGen
    /usr/bin/ld: cannot find -lLLVMObjCARCOpts
    /usr/bin/ld: cannot find -lLLVMScalarOpts
    /usr/bin/ld: cannot find -lLLVMInstCombine
    /usr/bin/ld: cannot find -lLLVMTransformUtils
    /usr/bin/ld: cannot find -lLLVMipa
    /usr/bin/ld: cannot find -lLLVMAnalysis
    /usr/bin/ld: cannot find -lLLVMRuntimeDyld
    /usr/bin/ld: cannot find -lLLVMExecutionEngine
    /usr/bin/ld: cannot find -lLLVMTarget
    /usr/bin/ld: cannot find -lLLVMMC
    /usr/bin/ld: cannot find -lLLVMObject
    /usr/bin/ld: cannot find -lLLVMCore
    /usr/bin/ld: cannot find -lLLVMSupport
    collect2: ld returned 1 exit status
    error: command 'g++' failed with exit status 1
    Complete output from command /home/msarahan/anaconda/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip_build_msarahan/xdress/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-dG7z3X-record/install-record.txt --single-version-externally-managed --compile:
   

XXXXXXX       XXXXXXXDDDDDDDDDDDDD

X:::::X       X:::::XD::::::::::::DDD

X:::::X       X:::::XD:::::::::::::::DD

X::::::X     X::::::XDDD:::::DDDDD:::::D

XXX:::::X   X:::::XXX  D:::::D    D:::::D

   X:::::X X:::::X     D:::::D     D:::::D

    X:::::X:::::X      D:::::D     D:::::D

     X:::::::::X       D:::::D     D:::::D

     X:::::::::X       D:::::D     D:::::D

    X:::::X:::::X      D:::::D     D:::::D

   X:::::X X:::::X     D:::::D     D:::::D

XXX:::::X   X:::::XXX  D:::::D    D:::::D

X::::::X     X::::::XDDD:::::DDDDD:::::D

X:::::X       X:::::XD:::::::::::::::DD

X:::::X       X:::::XD::::::::::::DDD

XXXXXXX       XXXXXXXDDDDDDDDDDDDD



using llvm-config from /home/msarahan/anaconda/bin/llvm-config

running install

running build

running build_py

creating build

creating build/lib.linux-x86_64-2.7

creating build/lib.linux-x86_64-2.7/xdress

copying xdress/astparsers.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/version.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/stlwrap.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/main.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/utils.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/typesystem.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/descfilter.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/base.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/dtypes.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/extratypes.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/autodescribe.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/pep8names.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/cythongen.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/doxygen.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/plugins.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/autoall.py -> build/lib.linux-x86_64-2.7/xdress

copying xdress/__init__.py -> build/lib.linux-x86_64-2.7/xdress

creating build/lib.linux-x86_64-2.7/xdress/clang

copying xdress/clang/cindex.py -> build/lib.linux-x86_64-2.7/xdress/clang

copying xdress/clang/enumerations.py -> build/lib.linux-x86_64-2.7/xdress/clang

copying xdress/clang/__init__.py -> build/lib.linux-x86_64-2.7/xdress/clang

creating build/lib.linux-x86_64-2.7/xdress/_enum

copying xdress/_enum/test_enum.py -> build/lib.linux-x86_64-2.7/xdress/_enum

copying xdress/_enum/__init__.py -> build/lib.linux-x86_64-2.7/xdress/_enum

copying xdress/_enum/enum.py -> build/lib.linux-x86_64-2.7/xdress/_enum

copying xdress/xdress_extra_types.pxd -> build/lib.linux-x86_64-2.7/xdress

copying xdress/xdress_extra_types.pyx -> build/lib.linux-x86_64-2.7/xdress

copying xdress/xdress_extra_types.h -> build/lib.linux-x86_64-2.7/xdress

copying xdress/_enum/LICENSE -> build/lib.linux-x86_64-2.7/xdress/_enum

copying xdress/_enum/README -> build/lib.linux-x86_64-2.7/xdress/_enum

running build_ext

building 'xdress.clang.libclang' extension

g++ -pthread -shared -L/home/msarahan/anaconda/lib -lclangTooling -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangStaticAnalyzerFrontend -lclangStaticAnalyzerCheckers -lclangStaticAnalyzerCore -lclangAnalysis -lclangARCMigrate -lclangEdit -lclangRewriteCore -lclangAST -lclangLex -lclangBasic -lpython2.7 -o build/lib.linux-x86_64-2.7/xdress/clang/libclang.so -L/home/msarahan/anaconda/lib -lz -lpthread -lrt -ldl -lm -lLLVMInstrumentation -lLLVMArchive -lLLVMLinker -lLLVMIRReader -lLLVMBitReader -lLLVMAsmParser -lLLVMDebugInfo -lLLVMOption -lLLVMipo -lLLVMVectorize -lLLVMBitWriter -lLLVMTableGen -lLLVMSystemZCodeGen -lLLVMSystemZAsmParser -lLLVMSystemZDesc -lLLVMSystemZInfo -lLLVMSystemZAsmPrinter -lLLVMHexagonCodeGen -lLLVMHexagonAsmPrinter -lLLVMHexagonDesc -lLLVMHexagonInfo -lLLVMNVPTXCodeGen -lLLVMNVPTXDesc -lLLVMNVPTXInfo -lLLVMNVPTXAsmPrinter -lLLVMMBlazeDisassembler -lLLVMMBlazeCodeGen -lLLVMMBlazeDesc -lLLVMMBlazeAsmPrinter -lLLVMMBlazeAsmParser -lLLVMMBlazeInfo -lLLVMCppBackendCodeGen -lLLVMCppBackendInfo -lLLVMMSP430CodeGen -lLLVMMSP430Desc -lLLVMMSP430Info -lLLVMMSP430AsmPrinter -lLLVMXCoreDisassembler -lLLVMXCoreCodeGen -lLLVMXCoreDesc -lLLVMXCoreInfo -lLLVMXCoreAsmPrinter -lLLVMMipsDisassembler -lLLVMMipsCodeGen -lLLVMMipsAsmParser -lLLVMMipsDesc -lLLVMMipsInfo -lLLVMMipsAsmPrinter -lLLVMARMDisassembler -lLLVMARMCodeGen -lLLVMARMAsmParser -lLLVMARMDesc -lLLVMARMInfo -lLLVMARMAsmPrinter -lLLVMAArch64Disassembler -lLLVMAArch64CodeGen -lLLVMAArch64AsmParser -lLLVMAArch64Desc -lLLVMAArch64Info -lLLVMAArch64AsmPrinter -lLLVMAArch64Utils -lLLVMPowerPCCodeGen -lLLVMPowerPCDesc -lLLVMPowerPCAsmPrinter -lLLVMPowerPCAsmParser -lLLVMPowerPCInfo -lLLVMSparcCodeGen -lLLVMSparcDesc -lLLVMSparcInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInterpreter -lLLVMMCJIT -lLLVMJIT -lLLVMCodeGen -lLLVMObjCARCOpts -lLLVMScalarOpts -lLLVMInstCombine -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMRuntimeDyld -lLLVMExecutionEngine -lLLVMTarget -lLLVMMC -lLLVMObject -lLLVMCore -lLLVMSupport

/usr/bin/ld: cannot find -lLLVMInstrumentation

/usr/bin/ld: cannot find -lLLVMArchive

/usr/bin/ld: cannot find -lLLVMLinker

/usr/bin/ld: cannot find -lLLVMIRReader

/usr/bin/ld: cannot find -lLLVMBitReader

/usr/bin/ld: cannot find -lLLVMAsmParser

/usr/bin/ld: cannot find -lLLVMDebugInfo

/usr/bin/ld: cannot find -lLLVMOption

/usr/bin/ld: cannot find -lLLVMipo

/usr/bin/ld: cannot find -lLLVMVectorize

/usr/bin/ld: cannot find -lLLVMBitWriter

/usr/bin/ld: cannot find -lLLVMTableGen

/usr/bin/ld: cannot find -lLLVMSystemZCodeGen

/usr/bin/ld: cannot find -lLLVMSystemZAsmParser

/usr/bin/ld: cannot find -lLLVMSystemZDesc

/usr/bin/ld: cannot find -lLLVMSystemZInfo

/usr/bin/ld: cannot find -lLLVMSystemZAsmPrinter

/usr/bin/ld: cannot find -lLLVMHexagonCodeGen

/usr/bin/ld: cannot find -lLLVMHexagonAsmPrinter

/usr/bin/ld: cannot find -lLLVMHexagonDesc

/usr/bin/ld: cannot find -lLLVMHexagonInfo

/usr/bin/ld: cannot find -lLLVMNVPTXCodeGen

/usr/bin/ld: cannot find -lLLVMNVPTXDesc

/usr/bin/ld: cannot find -lLLVMNVPTXInfo

/usr/bin/ld: cannot find -lLLVMNVPTXAsmPrinter

/usr/bin/ld: cannot find -lLLVMMBlazeDisassembler

/usr/bin/ld: cannot find -lLLVMMBlazeCodeGen

/usr/bin/ld: cannot find -lLLVMMBlazeDesc

/usr/bin/ld: cannot find -lLLVMMBlazeAsmPrinter

/usr/bin/ld: cannot find -lLLVMMBlazeAsmParser

/usr/bin/ld: cannot find -lLLVMMBlazeInfo

/usr/bin/ld: cannot find -lLLVMCppBackendCodeGen

/usr/bin/ld: cannot find -lLLVMCppBackendInfo

/usr/bin/ld: cannot find -lLLVMMSP430CodeGen

/usr/bin/ld: cannot find -lLLVMMSP430Desc

/usr/bin/ld: cannot find -lLLVMMSP430Info

/usr/bin/ld: cannot find -lLLVMMSP430AsmPrinter

/usr/bin/ld: cannot find -lLLVMXCoreDisassembler

/usr/bin/ld: cannot find -lLLVMXCoreCodeGen

/usr/bin/ld: cannot find -lLLVMXCoreDesc

/usr/bin/ld: cannot find -lLLVMXCoreInfo

/usr/bin/ld: cannot find -lLLVMXCoreAsmPrinter

/usr/bin/ld: cannot find -lLLVMMipsDisassembler

/usr/bin/ld: cannot find -lLLVMMipsCodeGen

/usr/bin/ld: cannot find -lLLVMMipsAsmParser

/usr/bin/ld: cannot find -lLLVMMipsDesc

/usr/bin/ld: cannot find -lLLVMMipsInfo

/usr/bin/ld: cannot find -lLLVMMipsAsmPrinter

/usr/bin/ld: cannot find -lLLVMARMDisassembler

/usr/bin/ld: cannot find -lLLVMARMCodeGen

/usr/bin/ld: cannot find -lLLVMARMAsmParser

/usr/bin/ld: cannot find -lLLVMARMDesc

/usr/bin/ld: cannot find -lLLVMARMInfo

/usr/bin/ld: cannot find -lLLVMARMAsmPrinter

/usr/bin/ld: cannot find -lLLVMAArch64Disassembler

/usr/bin/ld: cannot find -lLLVMAArch64CodeGen

/usr/bin/ld: cannot find -lLLVMAArch64AsmParser

/usr/bin/ld: cannot find -lLLVMAArch64Desc

/usr/bin/ld: cannot find -lLLVMAArch64Info

/usr/bin/ld: cannot find -lLLVMAArch64AsmPrinter

/usr/bin/ld: cannot find -lLLVMAArch64Utils

/usr/bin/ld: cannot find -lLLVMPowerPCCodeGen

/usr/bin/ld: cannot find -lLLVMPowerPCDesc

/usr/bin/ld: cannot find -lLLVMPowerPCAsmPrinter

/usr/bin/ld: cannot find -lLLVMPowerPCAsmParser

/usr/bin/ld: cannot find -lLLVMPowerPCInfo

/usr/bin/ld: cannot find -lLLVMSparcCodeGen

/usr/bin/ld: cannot find -lLLVMSparcDesc

/usr/bin/ld: cannot find -lLLVMSparcInfo

/usr/bin/ld: cannot find -lLLVMX86Disassembler

/usr/bin/ld: cannot find -lLLVMX86AsmParser

/usr/bin/ld: cannot find -lLLVMX86CodeGen

/usr/bin/ld: cannot find -lLLVMSelectionDAG

/usr/bin/ld: cannot find -lLLVMAsmPrinter

/usr/bin/ld: cannot find -lLLVMX86Desc

/usr/bin/ld: cannot find -lLLVMX86Info

/usr/bin/ld: cannot find -lLLVMX86AsmPrinter

/usr/bin/ld: cannot find -lLLVMX86Utils

/usr/bin/ld: cannot find -lLLVMMCDisassembler

/usr/bin/ld: cannot find -lLLVMMCParser

/usr/bin/ld: cannot find -lLLVMInterpreter

/usr/bin/ld: cannot find -lLLVMMCJIT

/usr/bin/ld: cannot find -lLLVMJIT

/usr/bin/ld: cannot find -lLLVMCodeGen

/usr/bin/ld: cannot find -lLLVMObjCARCOpts

/usr/bin/ld: cannot find -lLLVMScalarOpts

/usr/bin/ld: cannot find -lLLVMInstCombine

/usr/bin/ld: cannot find -lLLVMTransformUtils

/usr/bin/ld: cannot find -lLLVMipa

/usr/bin/ld: cannot find -lLLVMAnalysis

/usr/bin/ld: cannot find -lLLVMRuntimeDyld

/usr/bin/ld: cannot find -lLLVMExecutionEngine

/usr/bin/ld: cannot find -lLLVMTarget

/usr/bin/ld: cannot find -lLLVMMC

/usr/bin/ld: cannot find -lLLVMObject

/usr/bin/ld: cannot find -lLLVMCore

/usr/bin/ld: cannot find -lLLVMSupport

collect2: ld returned 1 exit status

error: command 'g++' failed with exit status 1

----------------------------------------
Cleaning up...
Command /home/msarahan/anaconda/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip_build_msarahan/xdress/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-dG7z3X-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip_build_msarahan/xdress
Storing debug log for failure in /home/msarahan/.pip/pip.log


Anthony Scopatz

unread,
Mar 3, 2014, 2:16:30 AM3/3/14
to Michael Sarahan, conda, xdress
Hi Michael, 

Thanks for reporting.  This seems like more of a conda / Anaconda issue.  I have CC'd them here.  It definitely seems like there is some issue with Clang versions or installation.  (Does Anaconda even include clang, or does it just include llvm? I don't actually know.)  I know that when I use stock ubuntu, everything is fine.

If you can, you might try seeing if you can get away with using GCC-XML.  It is slower and doesn't fully support C++ but might have the distinct advantage of actually working!

Thanks for reporting and let us know if you continue to struggle or what the fix ended up being!

Be Well
Anthony


--
You received this message because you are subscribed to the Google Groups "xdress" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/xdress/195842bc-024b-4c11-9bc9-5afcb6380e29%40googlegroups.com.

Anthony Scopatz

unread,
Mar 3, 2014, 2:18:46 AM3/3/14
to Michael Sarahan, conda, xdress
On Mon, Mar 3, 2014 at 1:16 AM, Anthony Scopatz <sco...@gmail.com> wrote:
Hi Michael, 

Thanks for reporting.  This seems like more of a conda / Anaconda issue.  I have CC'd them here.  It definitely seems like there is some issue with Clang versions or installation.  (Does Anaconda even include clang, or does it just include llvm? I don't actually know.)  I know that when I use stock ubuntu, everything is fine.

If you can, you might try seeing if you can get away with using GCC-XML.  It is slower and doesn't fully support C++ but might have the distinct advantage of actually working!

err fully support C++11, I mean.

Jinsuo Nie

unread,
Mar 3, 2014, 7:13:13 PM3/3/14
to xdr...@googlegroups.com
Fyr,a similar path issue occured to me when i tried clang on mingw.

chris.jor...@gmail.com

unread,
Apr 6, 2014, 10:15:05 PM4/6/14
to xdr...@googlegroups.com
This same issue just bit me on Ubuntu 12.04 w/ Anaconda. I could install xdress when Anaconda was removed from the path, but that doesn't install to the Anaconda python. 

Any suggestions for a workaround? 

Anthony Scopatz

unread,
Apr 6, 2014, 11:05:44 PM4/6/14
to chris.jor...@gmail.com, conda, xdress
Hi Chris, 

So I highly suspect that  this is problem with conda or anaconda and not xdress.  It seems very likely to me that the clang or llvm packages for conda is insufficient.  If you are seeing the same errors as Michael, then this is probably still the case.  

Hopefully, the conda folks (CC'd here) won't be silent on this issue again. I believe that there might be some interest in an xdress conda recipe on their end and so hopefully they can offer some guidance or advice.  I'd love to be proven wrong and that this is an xdress issue. I'll happily accept any patches that fix or workaround this issue.

Barring the above, the only work around that I can think of is to install clang from scratch on into the conda location.  Not ideal, I know.

Be Well
Anthony


--
You received this message because you are subscribed to the Google Groups "xdress" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/xdress/2490863c-3e83-4638-b1d5-630e41c08180%40googlegroups.com.

chris.jor...@gmail.com

unread,
Apr 6, 2014, 11:39:15 PM4/6/14
to xdr...@googlegroups.com, chris.jor...@gmail.com, conda
Thanks for the quick reply! 

That's unfortunate. Especially since trying to make sure whatever version of clang I downloaded/built is exactly compatible with the version shipped with Anaconda would be frustrating. I'm also not a big fan of Anaconda's clang and clang++ shadowing my clang/clang++.

I ping'd the Anaconda google group here: https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/NY4k7mh4-yA. Hopefully they'll either have a simpler workaround or fix it in an upcoming release. 

-Chris

Nathan Goldbaum

unread,
Apr 6, 2014, 11:48:05 PM4/6/14
to chris.jor...@gmail.com, xdr...@googlegroups.com
It looks like there *is* a clang binary included with anaconda.  That said, it looks like they've built a minimal build of clang that doesn't include some of the code analysis libraries like LibTooling.

I think the fix would be to build LLVM including all optional libraries - at least the ones supplied by the debian packagers for the LLVM you have installed on your ubuntu machine.

Unfortunately there is no LLVM recipe in the conda-recipes [1] repository, so I don't see a straightforward way to build LLVM under conda.

Anthony: you may have more success mailing the anaconda support list (anac...@continuum.io) rather than the conda support list (co...@continuum.io), since this is an issue with the LLVM package on the anaconda python distribution rather than the conda tool itself.


--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at http://groups.google.com/a/continuum.io/group/conda/.

Nathan Goldbaum

unread,
Apr 6, 2014, 11:48:43 PM4/6/14
to chris.jor...@gmail.com, xdr...@googlegroups.com
Argh, forgot to link ton conda-recipes: https://github.com/conda/conda-recipes

Anthony Scopatz

unread,
Apr 6, 2014, 11:58:10 PM4/6/14
to Nathan Goldbaum, Christopher Jordan-Squire, xdress
Thanks for the info Nathan!  Hopefully this can be fixed soon.


Anthony Scopatz

unread,
Apr 16, 2014, 12:46:47 AM4/16/14
to Travis Oliphant, Christopher Jordan-Squire, xdress, conda

On Mon, Apr 14, 2014 at 11:49 PM, Travis Oliphant <tra...@continuum.io> wrote:
Anaconda does not come with clang as far as I know --- I could be wrong about that.    It only includes llvm and its libraries which should be in $PREFIX/lib for any environment at $PREFIX.   There might be someone who has made a package of clang, but I don't know if it's useful.  

Hi Travis, 

Thanks for the clarification.  I think part of the trouble may be that you need to build clang *with* llvm - though you can build llvm on its own.  I have only done this a couple of times so I am not 100% on this.  Geoffrey may know more. And because clang & llvm change so often, the version of clang that you activate has to be exactly the same as the version of llvm that is activated.

So I am assuming that the problem that Chris et al. have run into is that the system version of clang does not match the anaconda version of llvm. That this would fail is not surprising :).

Putting words in Chris' mouth, in an ideal world anaconda would come with clang. In a reasonable world, someone would post a clang + llvm package to binstar. 

 
The xdress recipe will need to be able to pick up the clang libraries from somewhere.   I don't know how xdress is finding the clang libraries when you use gcc to compile? 

There is some llvm-config magic in xdress that solves this.
 
The only thing I can think of that is different about your version of Python in Anaconda is that it is located at another $PREFIX location.   Perhaps xdress assumes that the path to the clang libraries is related to $PREFIX?   Is there somebody that can provide some insight into this? 

There is no way to both 1) install clang into an environment, 2) activate that environment, and 3) not have clang "shadow" your system clang.  That is the purpose of activating an environment --- to specify which binaries you want to run.    So, I'm not sure what you are expecting here.

I would look for a solution that allows xdress to find the system libraries where CLANG is located.  Setting LIBRARY_PATH envrionment variable to the location of the clang libraries should also help. 

Chris, I think another temporary solution would be for you to create an environment *without* llvm but with everything else that you need.  Activate this when using xdress and have clang installed on your system.  Could you try this and let us know if it works?
 

A recipe for building xdress would be very welcome. 

Definitely!  XDress is pretty straightforward to install and I don't think this would be hard.  The trickier part is getting recipes for the GCC-XML and Clang.  Thanks again.

Be Well
Anthony
 

Best,

-Travis



--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at http://groups.google.com/a/continuum.io/group/conda/.



--

Travis Oliphant
CEO
Continuum Analytics, Inc.

--

Nathan Goldbaum

unread,
Apr 16, 2014, 1:01:44 AM4/16/14
to Anthony Scopatz, Travis Oliphant, Christopher Jordan-Squire, xdress, conda
On Tue, Apr 15, 2014 at 9:46 PM, Anthony Scopatz <sco...@gmail.com> wrote:

On Mon, Apr 14, 2014 at 11:49 PM, Travis Oliphant <tra...@continuum.io> wrote:
Anaconda does not come with clang as far as I know --- I could be wrong about that.    It only includes llvm and its libraries which should be in $PREFIX/lib for any environment at $PREFIX.   There might be someone who has made a package of clang, but I don't know if it's useful.  

Hi Travis, 

Thanks for the clarification.  I think part of the trouble may be that you need to build clang *with* llvm - though you can build llvm on its own.  I have only done this a couple of times so I am not 100% on this.  Geoffrey may know more. And because clang & llvm change so often, the version of clang that you activate has to be exactly the same as the version of llvm that is activated.

So I am assuming that the problem that Chris et al. have run into is that the system version of clang does not match the anaconda version of llvm. That this would fail is not surprising :).

Putting words in Chris' mouth, in an ideal world anaconda would come with clang. In a reasonable world, someone would post a clang + llvm package to binstar. 

FWIW, I do seem to have a clang binary in my anaconda installation, at least on 64 bit linux:

$ which clang
/home/goldbaum/anaconda/bin/clang

I'm not familiar enough with conda to know if there is a way to determine which conda package it is associated with.  I don't see recipes for either llvm or clang on the conda-recipes github page.  Is there a way to get the recipe from the conda package somehow?

Anthony Scopatz

unread,
Apr 16, 2014, 1:03:57 AM4/16/14
to Nathan Goldbaum, Travis Oliphant, Christopher Jordan-Squire, xdress, conda
On Wed, Apr 16, 2014 at 12:01 AM, Nathan Goldbaum <natha...@gmail.com> wrote:



On Tue, Apr 15, 2014 at 9:46 PM, Anthony Scopatz <sco...@gmail.com> wrote:

On Mon, Apr 14, 2014 at 11:49 PM, Travis Oliphant <tra...@continuum.io> wrote:
Anaconda does not come with clang as far as I know --- I could be wrong about that.    It only includes llvm and its libraries which should be in $PREFIX/lib for any environment at $PREFIX.   There might be someone who has made a package of clang, but I don't know if it's useful.  

Hi Travis, 

Thanks for the clarification.  I think part of the trouble may be that you need to build clang *with* llvm - though you can build llvm on its own.  I have only done this a couple of times so I am not 100% on this.  Geoffrey may know more. And because clang & llvm change so often, the version of clang that you activate has to be exactly the same as the version of llvm that is activated.

So I am assuming that the problem that Chris et al. have run into is that the system version of clang does not match the anaconda version of llvm. That this would fail is not surprising :).

Putting words in Chris' mouth, in an ideal world anaconda would come with clang. In a reasonable world, someone would post a clang + llvm package to binstar. 

FWIW, I do seem to have a clang binary in my anaconda installation, at least on 64 bit linux:

$ which clang
/home/goldbaum/anaconda/bin/clang

Oh sweet!  That is a lead.

Anthony Scopatz

unread,
Apr 16, 2014, 11:38:41 PM4/16/14
to Ilan Schnell, Nathan Goldbaum, Travis Oliphant, Christopher Jordan-Squire, xdress, conda
Interesting, 

@Chris, what version of anaconda are you on?

@Ilan, what is the result of the bash command "$ which clang"


On Wed, Apr 16, 2014 at 8:21 AM, Ilan Schnell <il...@continuum.io> wrote:
clang is part of the llvm package (on Linux only):
$ conda package --which ~/a150/bin/clang
/home/ilan/a150/bin/clang                           llvm-3.3-0

- Ilan

Christopher Jordan-Squire

unread,
Apr 19, 2014, 1:53:34 PM4/19/14
to Ilan Schnell, Anthony Scopatz, Nathan Goldbaum, Travis Oliphant, xdress, conda
Fun Fact: gmail apparently doesn't always auto-update or notify you when comments have been made to a google group thread you've commented on. So, sorry for the delayed response. 

I'm running Anaconda 1.9.2 on Ubuntu 12.04. And, like Nathan, there's a version of clang in ~/anaconda/bin/clang that's different from my system clang. Not very different, though, since they're both clang 3.3. 

Trying to install xdress on a new conda environment without clang & llvm was a great suggestion. That works, as long as you remember to add pip as an initial package for the new conda environment. (It tried to install xdress to my system python if I forgot to do that.) I ran the tests in the current head xdress's master branch and there were 5 failed unit tests, though. But the examples in the xdress tutorial seemed to work with the xdress installed from pip.


On Wed, Apr 16, 2014 at 8:40 PM, Ilan Schnell <il...@continuum.io> wrote:
$ which clang
/home/ilan/a150/bin/clang

- Ilan

Anthony Scopatz

unread,
Apr 19, 2014, 2:14:20 PM4/19/14
to Christopher Jordan-Squire, Ilan Schnell, Nathan Goldbaum, Travis Oliphant, xdress, conda
On Sat, Apr 19, 2014 at 12:53 PM, Christopher Jordan-Squire <chris.jor...@gmail.com> wrote:
Fun Fact: gmail apparently doesn't always auto-update or notify you when comments have been made to a google group thread you've commented on. So, sorry for the delayed response. 

I'm running Anaconda 1.9.2 on Ubuntu 12.04. And, like Nathan, there's a version of clang in ~/anaconda/bin/clang that's different from my system clang. Not very different, though, since they're both clang 3.3. 

Trying to install xdress on a new conda environment without clang & llvm was a great suggestion. That works, as long as you remember to add pip as an initial package for the new conda environment. (It tried to install xdress to my system python if I forgot to do that.) I ran the tests in the current head xdress's master branch and there were 5 failed unit tests, though. But the examples in the xdress tutorial seemed to work with the xdress installed from pip.

Hi Chris, 

Glad you got something working!  I think the unit test failures that you are seeing are because master has diverged from what is in pip (the latest release).

Be Well
Anthony
Reply all
Reply to author
Forward
0 new messages