Windows error codes ideomatically in HEX (and one hint)

[PallHaraldsson]

https://discourse.julialang.org/t/unable-to-precompile-any-packages/114311/18?u=palli

[PallHaraldsson]

It seems easier to Google Windows error codes in HEX, but that one got me though many false positives, at least not relating to that precompile issue.

[kimikage]

I think it is a misdirection to mention "LLVM" unless indeed most of the causes of the errors are LLVM related.

[PallHaraldsson]

Yes, I thought of that, why I only singled out that one error code. I don't know how common that one error code it is in general or that LLVM is the cause for it, but since people will blame Julia if some hint isn't provided, I think it's best to mention PATH and "e.g. LLVM". At least until we prevent the error for lld.exe, can we check PATH preemptively before invoking it? Until then, merge as is?

So I ran lld.exe - I received the following errors:

The procedure entry point _ZSt14__once_functor could not be located in the dynamic link library C:\Users\gplayer.julia\juliaup\julia-1.10.3+0.x64.w64.mingw32\libexec\julia\lld.exe

I'm not on Windows, I just debugged, found the cause and wanted others to benefit. It took a while to figure out, and only "some entry point" seems not good enough:

You can't know in general(?) what gets substituted for the those %hs:

# The procedure entry point %hs could not be located in the
# dynamic link library %hs.
# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0x139
# for hex 0x139 / decimal 313

[PallHaraldsson]

It seems easier to Google Windows error codes in HEX, but that one got me though many false positives, at least not relating to that precompile issue.

Now ok to merge with not mentioning LLVM? I still though it would have helped, don't want this PR simply be forgotten, and as is is also an improvement (for googlability).