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
still having an issue on OSX #7
Comments
Looks like a libc++/ libstdc++ mixing issue. On Tue, Sep 13, 2016, 17:53 J.Fischer notifications@github.com wrote:
|
My apologies for the late fix. This should be good now. About the issue where the configure script is prompting you to download all external dependencies, could you update your NativeTools repository, it should be fixed now. Thanks for testing :) |
Thank you. I encountered another issue.
But I am not sure that it is related to Nidium. |
Which version of OSX are you running ? Can you try the following command and report the output :
|
|
We need to support later osx sdk. I think we have to patch various deps configure files. |
Yes indeed. @jfroffice please note that Nidium has not been built/tested against OSX 10.12 (yet) so you may experience other issues. I have just commited a patch for portaudio, if you could try it :
|
@efyx thank you for your time. I have the following issue after your fix.
|
Hi, given the logs I believe it was because https://chromium.googlesource.com was unavailable. You could try again and it should work. |
I retry and get this error
|
Hi, you need, to install "yasm" software, since you are on OSX you can use brew : |
We should ship a binary of yasm. Brew is not installed by default on osx. On Mon, Oct 3, 2016, 15:35 efyx notifications@github.com wrote:
|
works now. +1 to ship a binary of yasm as https://github.com/Eloston/ungoogled-chromium |
After the last fix on OSX, I am still having an error after running
./configure_frontend
Moreover, it would be more comfortable to have the option to force the download of all external dependencies than having to answer [Y/n] for each dependency.
The text was updated successfully, but these errors were encountered: