This repository has been archived by the owner on May 20, 2024. It is now read-only.
holonix fails on big sur (darwin 11.2.1) #211
Comments
|
I upgraded to Big Sur 11.2.3, no change. |
|
Tagging: @thedavidmeister @steveej Also cross posted to forum: https://forum.holochain.org/t/holonix-fails-on-latest-macos-big-sur/5144 |
|
@harlantwood we've seen this issue before on Big Sur systems that were updated from Catalina. Can you confirm that is the case for you as well? |
@steveej yes, confirming that was my path to Big Sur. |
|
I have pretty much the same issue, although I'm on Big Sur 11.3 Beta (20E5210c). Here's my output: |
|
Do we have OSX CI where we could (try to) reproduce this @steveej ? |
We have a job set up on hydra which hasn't been showing this symptom. Also, I have tried to reproduce this locally in Big Sur VM without success, i.e. the build works successfully there. My conclusion so far that whatever is causing this issue is a consequence of updating from Catalyna to Big Sur. |
|
I'm running Catalina 10.15.7 on a Mid-2012 Retina MacBook Pro because it said my machine was too old for Big Sur and been trying to do the first exercise on the Holochain Gym. Whilst In the 'Getting started with a hApp' discussion forum topic, @guillemcordoba said:
and
So I tried just running One other little thing I did notice is they both broke on packages to do with random numbers. I don't think that's random. Anyway it's just gone midnight so I'm giving up for the night. |
Since this ticket is called "holonix fails on big sur (darwin 11.2.1)" and your report shows a different error message, you're likely dealing with a different issue than the reporter on this one. It would be helpful if you could file a new issue so we can deal with that separately. |
I posted on this issue as both issues are by the looks of it to do with linking, and as this issue is saying it is to do with a version of OSX I thought it would be helpful to say I'm experiencing similar kinds of issues because otherwise you might be focusing on something that isn't necessarily the cause of the issue. In the OP's original thread they said they had reinstalled nix since the upgrade, and also I noticed a couple of references to test VMs where you can't seem to reproduce the problem. That's my defence ;) I've got a busy day today but if I'm still experiencing issues when I next get to look at it tonight then I will create a new issue for sure, don't want to create one just yet but will if you want me to, but I still think it isn't just big sur... ;) |
|
@steveej here's the relevant chat transcript from previous conversations about this issue where it talks about sandboxing and linking from an issue 2 years ago so that's what gave me the impetus to append this issue with my similar-looking issues. If my issues are completely distinct then please accept my apologies, just trying to help as I know what it's like when you get caught in one train of thought as to the source of an issue!!!
|
|
@stephenbpurkiss I appreciate your chiming in to identify the root cause of the macOS issues. The sandbox idea sounded promising, however the manual says it's only enabled on linux by default. I might be overlooking something to I invite you to double-check that. |
Yup, it says disabled by default so thought I'd do a quick grep on the whole directory for
OK cool, just finished one task, got to grab some food and will have a go whilst I munch on salad! |
holochain's wasm sandbox is unrelated to the nix sandbox we're discussing here. I encourage you to (re-)read this link that I provided above: https://nixos.org/manual/nix/stable/#conf-sandbox . It describes which effect the setting has on
Looking forward to hearing your feedback 👍 |
|
Hm, the plot thickens: a forum user states that:
Sooooo maybe it's more specifically failing on my MacBook Pro, and not on all Mac hardware. In case it helps, mine is:
|
|
As an aside, I'm not currently blocked by this issue; I am working around by not using nix at all. Details here in case it's helpful to others: Using holochain on OSX Big Sur (without nix) |
|
Also I just tested again in case #212 affected this, with both: and ... and I get the same results as originally posted in this thread. |
This was referenced Apr 5, 2021
Closed
FYI I've just posted this to the developer exercises repo: |
|
I'm bumping against the same issue. I gave it my best shot at trying to figure out the problem, but I'm stuck. @steveej any chance you or someone else want to hop on a screen share and try to debug? Here's a summary of my findings.
Nix should be able to handle this, as it provides packages for Apple frameworks. I'm guessing that something needs to be tweaked in holonix/darwin/default.nix but I'm at a loss as to what [2][3]. I poked around for a while, but no luck (this is my first encounter with nix, so I'm not really effective at debugging, such as displaying it's environment variables during build, that would probably go a long way). References |
@tixel pointed me to this: |
Thank you, but I don't think that's related to this specific issue. Also tagging @thedavidmeister as author of |
|
Hey @mprimi
The holochain package build that fails for the OP happens before the nix-shell environment gets created. Hence any tweaks to the shell won't influence the build failure. If for some reason there is a linking bug in the dependency handling around frameworks we could experiment setting
Yes, I'm interested in taking a look as I haven't had my eyes and (remote) hands on a system that reproduces this failure. |
@steveej I really appreciate the responsiveness! Thank you. I can't find your contact info online, probably by design. :-) |
@steveej ping! I know there's other ways to set up a dev environment. But I really don't want to get my primary system "dirty". |
👍 Please check your inbox 🙂 |
|
Any update? I'm hitting the same problem when trying to run |
|
@jakintosh I have a call scheduled with Stefan to investigate this on my system. We'll let you know if we are successful. |
|
Just saw and tried this:
... about the same as before: |
|
Thanks @harlantwood Could you try out reinstalling the xcode command line tools as outline here? |
|
CoreFoundation seems to be a common issue with Big Sur:
It may be an issue that needs to be fixed in nix itself... Is there a Docker or Vagrant config around? They seem like they would be more stable options. Update: maybe getting closer to a fix: https://discourse.nixos.org/t/big-sur-frameworks-issue/10810 I tried this but it didn't fix anything, I don't know nix at all so not sure if this is the right direction or not. Apple really likes to break things for developers...Not a great intro to nix |
|
Maybe you guys can add a disclaimer to the getting started guide? That some folks (me included) have been seeing this big sur issue. I tried nearly everything over the last week. |
I tried this, and it did not help. Same errors. |
|
To everyone following this thread hitting build issues on macOS. I just sent this out to @mprimi and it occurred to me that there might be more people willing to try out my experiments and potentially hit more errors 😄 Please note that this is for debugging the build only for now and doesn't imply that the included holochain version is any good for happ development 😉 Try building the holochain nix package directlyThis instantiates a very recent version of holochain: Try out launching holonixThis launches a nix-shell which contains the aforementioned version of holochain: |
|
The post is unclear: should we be doing something with that script you posted before running those commands? or should we just try to run them? |
Thanks. I just decided to remove the cache setup from the message above. It occurred to me that it would be a less effective test if your systems wouldn't actually try to build the environment locally, as that is what has been failing and I'd like to verify. |
|
For the first command, after the downloading and vendoring stages I got this output: |
|
Apologies, the hashes are correct now. The same commands should continue further now. |
|
got all the way through the first command, and am now getting a hash mis-match on the second command
|
Apologies again. Please try once more. It's a pity these cases aren't detected by CI runs that make use of the cache, where the previous hashes are available and thus a mismatch goes undetected. /cc @mprimi |
|
seems like it worked! |
|
Same here. 🎉 Thank you @steveej ! |
|
Just tried it and it also worked for me Thank you @steveej. |
|
Works! @steveej FYI I did just:
without doing the nix-build command, and it worked fine: [nix-shell:~]$ hc --version
holochain_cli 0.1.0
[nix-shell:~]$ holochain --version
holochain 0.0.100
[nix-shell:~]$ lair-keystore --version
lair-keystore 0.0.1-alpha.12
[nix-shell:~]$ dna-util --version
dna-util 0.0.1 |
|
Thanks everyone for testing this! I'm glad to read it works now. If the build-time was bearable I'm tempted to merge #216 in and merge it through to |
|
I'm running a new 8-core i7 chip with 72GB of RAM so take it for what you will, but building the nix package and booting up the shell were both not an issue for me—i didn't time it, but it seemed like somewhere from 10-15 minutes. For now I'll follow whatever steps necessary to be able to keep up with the officially sanctioned dev environment (though whatever I've been able to build from this thread has at least given me some kind of environment to get hacking in). |
The first time I built it took a long time (~30m) but most of that time (~20m) was spent generating Rust documentation. 😅 Regardless. My 2c is that unblocking developers that want to check out and play with Holochain is definitely worth the slightly longer build time. |
@steveej I agree. The cache sounds like a good idea, but can always be a fast follow. |
I'm just on a macbook so honestly I expect hellish build times in the first place. It wasn't even that bad though, similar results to @mprimi but that's just an estimate (I also agree that developer access/simplicity is most important, imo). Would love to see this officially merged so I can get into experimenting without worrying about this experimental version not being fit for development. |
Hi @steveej, I was able to run the first command and it finished building successfully on a MBP 2018 with OS 11.5. However, when I run the second command, I get an HTTP 404 error, the package doesn't exist (anymore). Can you help me out please? |
|
@jost-s hey, these commands reference the branch experiment/holochain-darwin-ldflags which I deleted once the experiments were done. Everything you need should now be on the develop branch. The official installation guide at https://developer.holochain.org/install/#installing-the-holochain-dev-tools should work for you now! (@pdaoust in case it doesn't, where should bugs be filed?) |
|
@steveej Brilliant, confirmed that using nightly sources works fine 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Environment
Mac OS 11.2.1 (Big Sur)
Repro Steps
nix-shell https://holochain.love
or
nix-shell https://github.com/holochain/holonix/archive/develop.tar.gz
...both have the same issue
Errors
Output
The text was updated successfully, but these errors were encountered: