Exception pre-compiling DataArrays

New to Julia
1

Hello everyone,

I am in the very first steps with Julia. I would like to test the DataArrays packages, but it produces an exception during pre-compilation (reproduced below). Any tips on how to deal with this situation?

Thank you.

julia> using DataArrays
[ Info: Precompiling DataArrays [0fe7c1db-08c2-54a3-a222-6d1d3b7a471a]
ERROR: LoadError: LoadError: UndefVarError: start not defined
Stacktrace:
 [1] getproperty(::Module, ::Symbol) at ./sysimg.jl:13
 [2] top-level scope at none:0
 [3] include at ./boot.jl:317 [inlined]
 [4] include_relative(::Module, ::String) at ./loading.jl:1038
 [5] include at ./sysimg.jl:29 [inlined]
 [6] include(::String) at /home/duque004/.julia/packages/DataArrays/mcLPH/src/DataArrays.jl:3
 [7] top-level scope at none:0
 [8] include at ./boot.jl:317 [inlined]
 [9] include_relative(::Module, ::String) at ./loading.jl:1038
 [10] include(::Module, ::String) at ./sysimg.jl:29
 [11] top-level scope at none:2
 [12] eval at ./boot.jl:319 [inlined]
 [13] eval(::Expr) at ./client.jl:389
 [14] top-level scope at ./none:3
in expression starting at /home/duque004/.julia/packages/DataArrays/mcLPH/src/abstractdataarray.jl:27
in expression starting at /home/duque004/.julia/packages/DataArrays/mcLPH/src/DataArrays.jl:45
ERROR: Failed to precompile DataArrays [0fe7c1db-08c2-54a3-a222-6d1d3b7a471a] to /home/duque004/.julia/compiled/v1.0/DataArrays/ZAWTY.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] macro expansion at ./logging.jl:313 [inlined]
 [3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1184
 [4] macro expansion at ./logging.jl:311 [inlined]
 [5] _require(::Base.PkgId) at ./loading.jl:941
 [6] require(::Base.PkgId) at ./loading.jl:852
 [7] macro expansion at ./logging.jl:311 [inlined]
 [8] require(::Module, ::Symbol) at ./loading.jl:834
2

Looks like you’re on Julia 0.7 or 1.0? DataArrays doesn’t work there (and it’s not needed anyway, see this blog post).

3

Thanks. I am indeed working on Julia 1.0, but following a book that is outdated. The blog post explains what is wrong.

Best.