OOB during package build

iagobaapellaniz commented 7 years ago

Building CUDArt fails. After solving the rest of problems I encountered in the way, I get this error now, which I cannot solve

LoadError: BoundsError: attempt to access 0-element Array{String,1} at index [1]
...

I'm not an expert on this, so I can give more details if you want, but I preferred to keep the thread as simple as possible.

vchuravy commented 7 years ago

Can you post the full backtrace?

iagobaapellaniz commented 7 years ago

The version info shows this

Julia Version 0.5.2
Commit f4c6c9d (2017-05-06 16:34 UTC)
Platform Info:
  OS: Linux (x86_64-redhat-linux)
  CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT NO_AFFINITY NEHALEM)
  LAPACK: libopenblas64_
  LIBM: libopenlibm
  LLVM: libLLVM-3.7.1 (ORCJIT, broadwell)

If I try to build CUDArt I obtain this.

julia> Pkg.build("CUDArt")
INFO: Building CUDAdrv
INFO: CUDAdrv.jl has already been built for this set-up.
INFO: Building CUDArt
===============================[ ERROR: CUDArt ]================================

LoadError: BoundsError: attempt to access 0-element Array{String,1} at index [1]
while loading /home/iapellaniz/.julia/v0.5/CUDArt/deps/build.jl, in expression starting on line 380

================================================================================

================================[ BUILD ERRORS ]================================

WARNING: CUDArt had build errors.

 - packages with build errors remain installed in /home/iapellaniz/.julia/v0.5
 - build the package(s) and all dependencies with `Pkg.build("CUDArt")`
 - build a single package by running its `deps/build.jl` script

==============================================================================

Is this what you mean by full backtrace?

maleadt commented 7 years ago

The catch ex ... rethrow(ex) seems to ruin the backtrace -- anybody knows how come?

Anyway, try removing that and re-run build. That is, change CUDArt/deps/build.jl from:

try
    main()
catch ex
    # if anything goes wrong, wipe the existing ext.jl to prevent the package from loading
    rm(ext; force=true)
    rethrow(ex)
end

into

main()

and re-run Pkg.build. Now post the full back-trace.

timholy commented 7 years ago

Backtraces are much better on 0.6 so it would be worth checking there.

maleadt commented 7 years ago

Going to close this for lack of information. Please run deps/build.jl manually, ie. julia CUDArt/deps/build.jl instead of Pkg.build("CUDArt") as Pkg truncates the stacktrace.

Also, the build system has changed a bit, so this just might be fixed already.

iagobaapellaniz commented 7 years ago

I wasn't able to perform a build to obtain the related info since I installed everything from scratch.

I still have some problem but not related to this issue anymore.

Thanks anyway.

On Wed, Aug 9, 2017, 16:08 Tim Besard notifications@github.com wrote:

Going to close this for lack of information. Please run deps/build.jl manually, ie. julia CUDArt/deps/build.jl instead of Pkg.build("CUDArt") as Pkg truncates the stacktrace.

Also, the build system has changed a bit, so this just might be fixed already.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JuliaGPU/CUDArt.jl/issues/92#issuecomment-321266115, or mute the thread https://github.com/notifications/unsubscribe-auth/AFa33AQzNr-YGuXWpiwfMTAB63MGYOVvks5sWb1FgaJpZM4N-Np1 .

--

Dr. Iagoba Apellaniz

Dept. Theoretical Physics - Uni. of the Basque Country (UPV/EHU) https://sites.google.com/view/iapellaniz/physics

maleadt commented 7 years ago

I still have some problem but not related to this issue anymore.

If you do, just open another issue, or open a thread on Discourse. But please try and include a full backtrace + version/commit info, otherwise this kind of issue is really hard to debug.

JuliaAttic / CUDArt.jl

OOB during package build #92