-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Install Third Party script fails on double-conversion.build #21354
Labels
Comments
It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists. The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running |
Duplicate of #20774 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Environment
Environment:
OS: macOS High Sierra 10.13.6
Node: 10.11.0
Yarn: 1.10.1
npm: 6.4.1
Watchman: 4.9.0
Xcode: Xcode 10.0 Build version 10A255
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0
Description
On build step, running script 'Install Third Party' fails when executing 'double-conversion.build' build command:
In my
~/.rncache
, I have:There's a lot of chatter here regarding this, but many issues cite having the library within my
.rncache
.Per Issue #14447, I've tried creating a
third-party
folder in:node_modules/react-native/third-party
and placing libraries from my~/.rncache
there unzipped. Then, I need to manually configure glog.That results in error:
Per Issue #16106, I can alter
signalhandler.cc
:At Line 78, change:
return (void*)context->PC_FROM_UCONTEXT;
toreturn NULL;
Which then fails on: Building library libRCTWebSocket.a
Per Issue #16039, I can't get past changing the "fishhook.h" import.
Are there known issues with my environment, as this project runs on numerous other MacBooks.
Reproducible Demo
This is within the build, executing:
npm run build
The text was updated successfully, but these errors were encountered: