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
make
fails on 10.14.6 ("has __UNIXSTACK, but wrong ::maxprot (should be 7)")
#3
Comments
@dominiquelee, thanks for your report, it was reported on the bugtracker (https://bugs.kde.org/show_bug.cgi?id=399584) but it might be easier to debug here. I am using 10.14.6 as well and I don't get this issue. The problem should be fairly easy to fix but I want to be sure of what is going on. Could you please paste the output of |
Sure. |
Thanks, it is what I thought. I am finalising some other work and I will get on right after. |
Could you try the feature/xcode_check branch? |
@LouisBrunner , I have another error, even with xcode_check branch
Here is the output of ./configure command: |
On my side, it's indeed working fine. I guess it's worth adding I have Xcode 11.3.1 (11C504). |
@dominiquelee, thanks for the confirmation! @Akylzhan, I have run into a similar issue before, I think it was linked to a setup issue. |
Thank you very much for responding There is such directory in "Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/"
|
@Akylzhan, let's try the gcc route then. I forgot that you don't need to disable/remove your extra gcc, you can just force |
@LouisBrunner the same error occurred |
@Akylzhan I'll need the |
@LouisBrunner thanks for the support, now I have tried to install it again and valgrind installs with brew, but the new problem occurred when I used valgrind to check for mem.leaks in empty c++ executable and it shows many definitely lost leaks |
@Akylzhan That's a different problem, please create a new issue including the output of valgrind, what was expected, etc. |
On a Mojave 10.14.6, building the current master (a8e2879) with
results in
The text was updated successfully, but these errors were encountered: