Ha ha. The double negative.
I think Kristoffer is saying the debug version will not be included from v1.0.4 and v1.1.0
(the PR to remove debug will be in those versions)
OK, not that important but I’m confused because he also said
The PR to remove debug “will not be in v1.0.3 but will be in 1.1.0 and 1.0.4.”
Hence, debug will not be included from those later versions.
1 Like
Right, I got it now. While I was talking on the dll itself he was referring to the action to remove it. 
1 Like
Thanks for listing the offending lines, which lead me to this thread.
Deleting the second entry [[Pkg-93b6d6de857dc88e665d2c64397852ab9701ba24]]
was necessary, but not sufficient.
With these commands the build was clean:
git checkout v1.0.3
# clean the repo; both the following commands were mandatory.
git reset --hard
make cleanall
# verify
git status
HEAD detached at v1.0.3
nothing to commit, working tree clean
# build
make -j $(nproc)
make docs
What did you end up doing? I’ve tried cleaning most things now but I’m still getting this.
I made a bunch of noise about it on Slack (which was ignored), added it to the 1.1 milestone on GitHub (also ignored). Ultimately 1.0.3 was released without fixing this. I’m not sure how that was deemed acceptable, but I was on vacation at the time so there wasn’t much I could do about it.
The issue was not ignored, in fact the issue (JL_LLVM_VERSION not defined in codegen_shared.h (in llvmcalltest.cpp) · Issue #30379 · JuliaLang/julia · GitHub) got fixed by the PR (Disable a test on 1.0.3 causing warnings during compilation by KristofferC · Pull Request #30422 · JuliaLang/julia · GitHub).
No, 1.0.3 was released with fixing this, Disable a test on 1.0.3 causing warnings during compilation by KristofferC · Pull Request #30422 · JuliaLang/julia · GitHub was merged into release-1.0.
The issue is still open, so that’s a bit hard to tell.
Just tried this but I’m still getting the error. I initially tried building v1.1 but I’m also seeing this when trying to build master (same local repo).
That sounds odd then. Are you sure it is the same warnings?
Pretty sure. In both cases, I get
client.jl
docs/Docs.jl
Base ─────────── 26.535253 seconds
error during bootstrap:
LoadError("sysimg.jl", 491, ArgumentError("Package Base64 not found in current path:\n- Run `import Pkg$
Pkg.add(\"Base64\")` to install the Base64 package.\n"))
rec_backtrace at /data/andreasnoack/julia/src/stackwalk.c:94
record_backtrace at /data/andreasnoack/julia/src/task.c:217 [inlined]
jl_throw at /data/andreasnoack/julia/src/task.c:417
require at ./loading.jl:823
jl_fptr_trampoline at /data/andreasnoack/julia/src/gf.c:1854
jl_apply_generic at /data/andreasnoack/julia/src/gf.c:2209
do_call at /data/andreasnoack/julia/src/interpreter.c:323
eval_value at /data/andreasnoack/julia/src/interpreter.c:411
eval_body at /data/andreasnoack/julia/src/interpreter.c:625
jl_interpret_toplevel_thunk_callback at /data/andreasnoack/julia/src/interpreter.c:885
Interpreter frame (ip: 40)
Core.CodeInfo(code=Array{Any, (87,)}[
Expr(:call, Base.getproperty, :Base, :(:is_primary_base_module)),
Expr(:gotoifnot, SSAValue(1), 87),
<newvar #<3>>,
<newvar #<8>>,
...
which looks slightly different from Stefan’s error message, though.
Oh, I thought we were talking about https://github.com/JuliaLang/julia/issues/30379 (which is what Stefan was talking about).
Regarding that error, only thing I can think is that the LOAD_PATH is messed up somehow. Maybe you can print it out before the stdlibs are loading.
That was unfortunate.
It’s
docs/Docs.jl
LOAD_PATH: ["@stdlib"]
Base ─────────── 26.609290 seconds
right before the stdlib section of sysimg.jl. Is that right?
That is what it should be afaik.
I recognize this as a variant of KeyError: key "Pkg" not found · Issue #965 · JuliaLang/Pkg.jl · GitHub so try to clean usr (e.g. stdlib-git: improve integration with git-external by vtjnash · Pull Request #30075 · JuliaLang/julia · GitHub), or at least wipe out stdlib/Pkg.
Thanks. That did it.