Closed krux02 closed 4 years ago
what logic is this: https://github.com/nim-lang/nimble/blob/3d6dc90cd4dfc12b8ae9d1958e84610cf21b34bb/src/nimblepkg/version.nim#L215
req
= "nim >= 0.19.9 "
, but with more whitespace that got stripped, thanks to github.
The error message "Error: unhandled exception: No such file or directory [OSError]"
This is a bug. Any time Nimble crashes with a exception that isn't of type NimbleError
there is a bug. Running Nimble with the --debug
flag might be able to tell you what file it cannot find.
More discussion: https://irclogs.nim-lang.org/23-02-2019.html#13:05:32
@dom96 why do I need to pass a --debug
flag to get crucial information as that?
I'm not saying this is how it should be. I already acknowledged that this is a bug.
You use the --debug
flag to... you know... debug things. I'm not expecting you to use it routinely.
Unfortunately hello_triangle fails to compile for me so this doesn't get far enough:
/private/var/folders/qs/3mwpxj8s1td75h2bby7g18xw0000gn/T/nimble_79143/githubcom_krux02openglsandbox/glad/gl.nim(109, 39) Error: -1 can't be converted to uint64
I've tried to fix this error and managed to get quite far, but then got a C compile error and just gave up. Can you still repro this?
fancygl@0.3.2
doesn't work due to the above error reported by @dom96 but fancygl@#head
works fine. Seems like a Nim build issue and this goes back to Nimble not showing the output. The build error showed up with --debug. Closing this but there are other discussions about showing more output that are being debated.
when I try to install my package, it fails. But the problem is that I can't find out where the problem comes from. Here is the output of the process:
The error message "Error: unhandled exception: No such file or directory [OSError]" isn't helpful at all, because it doesn't tell what file it can't find.
The line information
../../../lib/pure/includes/oserr.nim(85)
is not helpful, because it just points toraiseOSError
. This is not wher the problem came from.Also it does not list the command that failed. So I can't rerun the commend and see if I can debug it somehow.
Last but not least it leaves a half way installed package in the file system that cannot be removed with
nimble uninstall
:The information above was printed with a nimble in release mode:
To debug the problem further, I tried to build a debug mode with this command (same nimble source)
But on debug, nimble doesn't even get that far:
Also while I try to find the problem with
nimble install fancygl
I run that command several times. The problem is that it downloads the entire project every time. This takes a lot of time and can be optimized.