Sorry, only the '+' before '=', no '+' at the beginning. Correct way:
LIB_DEPENDENCY += $(LIBDIR)/lib$(LLVM_LIB_NAME).$(SHLIB_EXT)
On Tuesday, September 6, 2016 at 2:08:54 PM UTC+8, K leo wrote:
>
> in deps/BuildBootstrap.Makefile, put '+' in the line so it becomes as
> follows:
>
> +LIB_DEPENDENCY += $(LIBDIR)/lib$(LLVM_LIB_NAME).$(SHLIB_EXT)
> Then Pkg.build("CXX")
>
> On Sunday, September 4, 2016 at 9:37:45 PM UTC+8, Uwe Fechner wrote:
>>
>> Could you explain your fix? I have the same error.
>>
>> Uwe
>>
>> On Sunday, September 4, 2016 at 6:22:36 AM UTC+2, K leo wrote:
>>>
>>> The error of adding Cxx was eliminated by changing small bits in the
>>> makefile. It builds successfully. I am so surprised to find that it is
>>> such a huge package with over 1GB in size.
>>>
>>> On Sunday, September 4, 2016 at 6:41:28 AM UTC+8, K leo wrote:
>>>>
>>>> Thanks very much for the advise.
>>>>
>>>> One question is whether Cxx is mature enough to be usable at this
>>>> stage. I tried to add it with Julia 0.5 and got the following errors:
>>>>
>>>> julia> Pkg.add("Cxx")
>>>> INFO: Installing Cxx v0.0.1
>>>> INFO: Building Cxx
>>>> writing path.jl file
>>>> Tuning for julia installation at:
>>>> /home/xxx/Software/julia-e6f843b073/bin
>>>> g++ -D_GLIBCXX_USE_CXX11_ABI=0 -fno-rtti -DLIBRARY_EXPORTS -fPIC -O0
>>>> -g -std=c++11
>>>> -I/home/xxx/Software/julia-e6f843b073/bin/../../src/support
>>>> -I/home/xxx/Software/julia-e6f843b073/bin/../include -Isrc/clang-3.7.1/lib
>>>> -Ibuild/clang-3.7.1/include -Isrc/clang-3.7.1/include
>>>> -Isrc/llvm-3.7.1/include -Ibuild/llvm-3.7.1/include -DLLVM_NDEBUG -c
>>>> ../src/bootstrap.cpp -o build/bootstrap.o
>>>> ../src/bootstrap.cpp:19:35: fatal error: llvm/ADT/DenseMapInfo.h: No
>>>> such file or directory
>>>> compilation terminated.
>>>> BuildBootstrap.Makefile:131: recipe for target 'build/bootstrap.o'
>>>> failed
>>>> make: *** [build/bootstrap.o] Error 1
>>>> =================================[ ERROR: Cxx
>>>> ]=================================
>>>>
>>>> LoadError: failed process: Process(`make -j2 -f BuildBootstrap.Makefile
>>>> BASE_JULIA_HOME=/home/xxx/Software/julia-e6f843b073/bin`,
>>>> ProcessExited(2))
>>>> [2]
>>>> while loading /home/xxx/.julia/v0.5/Cxx/deps/build.jl, in expression
>>>> starting on line 31
>>>>
>>>>
>>>> ================================================================================
>>>>
>>>> ================================[ BUILD ERRORS
>>>> ]================================
>>>>
>>>> WARNING: Cxx had build errors.
>>>>
>>>> - packages with build errors remain installed in /home/xxx/.julia/v0.5
>>>> - build the package(s) and all dependencies with `Pkg.build("Cxx")`
>>>> - build a single package by running its `deps/build.jl` script
>>>>
>>>>
>>>> ================================================================================
>>>> INFO: Package database updated
>>>>
>>>> On Saturday, September 3, 2016 at 9:17:38 AM UTC+8, Steven G. Johnson
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Friday, September 2, 2016 at 8:51:21 PM UTC-4, K leo wrote:
>>>>>>
>>>>>> While the majority of my analytics are in Julia, I will need to use
>>>>>> an external event handling API which is implemented in C++. It looks
>>>>>> that
>>>>>> I have two options: 1) write the main code in C++ with the API and call
>>>>>> Julia function for analytics; 2) write the main code also in Julia that
>>>>>> work seamlessly with my analytics and call the C++ API for events.
>>>>>>
>>>>>> Which would be the better path in terms of ease of coding and
>>>>>> performance?
>>>>>>
>>>>>
>>>>> Much easier to call C++ from Julia, particularly with the Cxx.jl
>>>>> package <https://github.com/Keno/Cxx.jl>. Performance-wise, it
>>>>> shouldn't matter, but it is always easier to write glue code in a
>>>>> higher-level language than in a lower-level language.
>>>>>
>>>>
