-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building release 1.6.6 on illumos-based OS fails #19914
Comments
PRs are welcome but we don't support "OmniOS" officially. |
Understood, thanks. Do you have any interest in supporting it? |
No, it's yet another Unix variant, totally uninteresting. |
Got it, thank you for clarifying. |
@szaydel I got this error on 10.6.8 Rosetta now. |
@barracuda156, let me look into this. I won't have cycles today, I don't think but I will look into it tomorrow. Can you tell me a little bit about what you have Omni running on, and the version of Omni? |
@szaydel Thanks for responding! I am getting this error with P. S. Precisely, I get this:
|
Yes, I think it is probably a nearly identical problem, likely a matter of workaround similar to what I had to do. I wish I could more easily repro this, but I don't have a mac with a PPC chip. |
@szaydel It may not occur on a PPC Mac natively (I am away from my PPC machines so cannot check atm). |
I did not right away realize that the example from 3 hours ago was not Omni. :) Yes, this seems to be a pretty particular setup. |
@szaydel I think now there is some problem with a packaged source of |
Interesting. Are you seeing this same problem building directly from tip of master? |
@szaydel Let me see. At the moment I use 1.6.6, but if that fails, I switch to latest-commit version. Limited free time these days, I just now made patches for Nim code so that correct compiler is invoked with correct arch flags. Running the build now. Expectations not high yet, I doubt |
@szaydel So yeah, I ended up with the same assert error in the second stage (after bootstrapping from C sources completed):
|
I have not tested yet on my M1 with Omni under UTM. I am going to try to find some time today. Sorry, time has been rather short... This latest output you shared, is this from the master branch? |
@szaydel Output above was from v. 1.6.6 (release), but, unfortunately, master branch fails the same way. I just switched to building from latest-commit Nim, and the same failure on the same spot:
|
Well, at least things are consistent, something to be said for that. :) |
@szaydel Just back to my PPC machines. Now we know for sure that assertion failure has nothing to do with Rosetta, same error on 10.6 PPC:
|
I need to test this on ARM, have not had a chance. On my intel x86-64 I did not have an issue. |
@Araq Maybe you could help here and give a hint, what may be going wrong? Notice that initially I had this error with older version of csources, but not with new ones: #19914 (comment) |
As the author of #13798. I think @timotheecour may be able to help. |
I just tried to build on recent OmniOS from https://nim-lang.org/download/nim-1.6.6.tar.xz and I hit a build failure.
Current Output
Possible Solution
I modified
build.sh
to instead of usinguname -m
to a hardcodedamd64
, which allows me to build without a problem. I think the solution here might be to check that this amounts toamd64
:...and if so, then use
amd64
instead of what otherwise ends-up beingi86pc
:The text was updated successfully, but these errors were encountered: