"can't load .so/.DLL" error with Symbol not found while installing optparse-applicative-0.13.2.0 dependency on mac via Stack for Hakyll stack install hakyll
#3559
Comments
archywillhe
changed the title
archywillhe
changed the title
|
May be related to this - #2577 We'll hopefully have a new stack release soon. Unlikely, but it might help to upgrade to the prerelease - https://github.com/commercialhaskell/stack/releases/tag/v1.6.0.20171022 It might also be helpful to use the latest |
archywillhe
changed the title
stack install hakyll
|
@mgsloan hey thanks for the pointer! Just got the prereleased stack but still run into the same problem. trying the |
|
Cool! Note that the issue is probably due to problems in the build of |
|
@mgsloan Oooh I see! Got it! Thanks! |
|
@mgsloan oh no I got a different symbol not found situation (with the same Symbol not found: |
|
Also, when i first tried It recommended me to add some dependencies for my before I was able to run |
|
Same/similar issue with optparse-applicative-0.14.2.0 on linux with cabal. I've got no idea how to resolve this. |
|
Same as above with Nix/NixOS: however, deleting most of Could this be due to a failed or incomplete (Ctrl+C) dependency still passing as successful? |
|
@unode Did you install |
|
@soulomoon As mentioned the issue went away with deleting |
|
I have the same issue (with Stack I worked around the issue by yanking my whole Other than a fix, if anyone knows of a good workaround to this problem that would be greatly appreciated!! |
|
For me downgrading to Stack v1.9.3 solved this. Perhaps this old bug came back in v2? |
|
This might be an issue with the dependency itself — see #4141. If one of you would try the solution at the end of the thread, we can work out how to proceed. |
If it was an issue with the dependency, why would removing I got this issue again as I've recently re-upgraded to stack v2, because the latest stackage isn't stack v1 compatible.. and now I suffer from this again :( :( :( It's time to check again if nix works on mac :( Man I hate computers |
|
So again I worked around this by removing Edit: second time today now purging |
I believe it's to do with temporary files. There's more detail in the issue. The fix involves a change to |
To be clear I'm suffering from the same symptom but not in |
|
It might be possible to be more selective in which files get deleted. You say |
|
Can you build all the dependencies, individually? As in #4969 |
No,
Unlike that issue, for me things do work fine after removing the stack files and rebuilding cleanly. The dependencies also can build individually successfully. |
|
More info: this doesn't seem to require a race with a concurrent Update: bumping a version of a hackage dependency may trigger a rebuild of the broken dependency and fix the build without yanking the whole |
|
Is this issue getting any attention?
|
|
This problem started occuring often again now after upgrading to stack 2.5.1 However the following works around it: |
|
I have a new theory on why this happens along with a new work-around that seems to work for me (the simple removing Theory: There are several Work-around: decode the missing symbol to figure out which library it should come from. Remove all the |
|
I'm running into this issue in 2022; stack 2.7.5 |
I regularly run into it. I suspect that if a Haskell library changes (potentially indirectly due to dependency) but it doesn't change its version number then there would be two |
|
I am closing this issue given the passage of time and that it seems to have been diagnosed: Stack assumes that immutable package versions are immutable and if they are not (they change) problems arise. |
I run into this error while installing the optparse-applicative dependency for hakyll via stack.
It is a "can't load .so/.DLL" error with an unfound symbol
_ansizmterminalzm0zi6zi3zi1zm3RTqikoQf47ajVD9m8zzgB_SystemziConsoleziANSIziCodes_csi_closureI've tried everything in this post such as
rm -r ~/.stack/snapshotsorstack cleanbut to no avail. I have even reinstalled my stack and the error persists.I am running stack Version 1.5.1 on macOS Sierra 10.12.6.
The text was updated successfully, but these errors were encountered: