-
Notifications
You must be signed in to change notification settings - Fork 24.9k
[precompile][ios] fixed cp command to work with gnu coreutils #54063
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
Conversation
When using gnu coreutils, installation of ReactNativeDependenices on iOS fails at compile time with errors like in the following issue (in the Expo repo): expo/expo#38992 This is caused by a missing `.` in the end of the path name that the built-in MacOS cp command handles well, but that will create an extra Headers folder when using cp from gnu coreutils. This commit fixes this by adding the missing `.`
|
I was losing hope, but you saved the day. Indeed, GNU utils were the issue. I've tried everything to fix Expo 54 not working on my macOS (as in #22703 (comment) and expo/expo#38992) and coreutils were the culprit. For anyone wondering what I did:
rm -rf ios/Pods
rm -rf ios/Podfile.lock
rm -rf ios/build
rm -rf ~/Library/Developer/Xcode/DerivedData
rm -rf ~/Library/Caches/CocoaPods/
rm -rf ~/.cocoapods/
pod cache clean --all |
|
This pull request was successfully merged by @chrfalch in 068ec39 When will my fix make it into a release? | How to file a pick request? |
|
Thanks for fixing this @chrfalch 🙏 |
Summary: When using gnu coreutils, installation of ReactNativeDependenices on iOS fails at compile time with errors like in the following issue (in the Expo repo): expo/expo#38992 This is caused by a missing `.` in the end of the path name that the built-in MacOS cp command handles well, but that will create an extra Headers folder when using cp from gnu coreutils. This commit fixes this by adding the missing `.` ## Changelog: [IOS] [FIXED] - Fixed issue when using gnu coreutils cp command when using precompiled binaries causing compilation error Pull Request resolved: #54063 Test Plan: - Verify that you're running gnu coreutils (`cp --version`) - Create new expo app `npx create-expo-app` - Build on iOS - should error without this fix, should work with the fix. Reviewed By: christophpurrer Differential Revision: D83964083 Pulled By: javache fbshipit-source-id: 46dc074ca9b7fc97fa5a37ef48d68a895e3310ff
|
This pull request was successfully merged by @chrfalch in 779c768 When will my fix make it into a release? | How to file a pick request? |
Summary: When using gnu coreutils, installation of ReactNativeDependenices on iOS fails at compile time with errors like in the following issue (in the Expo repo): expo/expo#38992 This is caused by a missing `.` in the end of the path name that the built-in MacOS cp command handles well, but that will create an extra Headers folder when using cp from gnu coreutils. This commit fixes this by adding the missing `.` ## Changelog: [IOS] [FIXED] - Fixed issue when using gnu coreutils cp command when using precompiled binaries causing compilation error Pull Request resolved: #54063 Test Plan: - Verify that you're running gnu coreutils (`cp --version`) - Create new expo app `npx create-expo-app` - Build on iOS - should error without this fix, should work with the fix. Reviewed By: christophpurrer Differential Revision: D83964083 Pulled By: javache fbshipit-source-id: 46dc074ca9b7fc97fa5a37ef48d68a895e3310ff
Summary:
When using gnu coreutils, installation of ReactNativeDependenices on iOS fails at compile time with errors like in the following issue (in the Expo repo):
expo/expo#38992
This is caused by a missing
.in the end of the path name that the built-in MacOS cp command handles well, but that will create an extra Headers folder when using cp from gnu coreutils.This commit fixes this by adding the missing
.Changelog:
[IOS] [FIXED] - Fixed issue when using gnu coreutils cp command when using precompiled binaries causing compilation error
Test Plan:
cp --version)npx create-expo-app