Skip to content
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

'config.h' file not found - mutex.h #22267

Closed
3 tasks done
MoKhajavi75 opened this issue Nov 14, 2018 · 17 comments
Closed
3 tasks done

'config.h' file not found - mutex.h #22267

MoKhajavi75 opened this issue Nov 14, 2018 · 17 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@MoKhajavi75
Copy link

Environment

React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
      Memory: 7.40 GB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.13.0 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
    IDEs:
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.1 => 16.6.1
      react-native: 0.57.5 => 0.57.5
    npmGlobalPackages:
      react-native-cli: 2.0.1

Description

As mentioned here, this must be fixed but i'm getting this error after using react-native init MyTestProject.

Reproducible Demo

Simply use react-native init MyTestProject and you will get this error!
Also, i tried to set the Project Settings to Legacy Build System and cleaned the build folder but no result!

@sabirbasha
Copy link

Am also facing same issue can someone help me to resolve this

@MoKhajavi75
Copy link
Author

Am also facing same issue can someone help me to resolve this

As a temporary fix, you could navigate to ..\node_modules\react-native\third-party\glog-0.3.5 and:

./configure
make

@fsarachu
Copy link

this solved my problem: #19529 (comment)

@thymikee
Copy link
Contributor

thymikee commented Nov 15, 2018

@facebook-github-bot duplicate #19529

If you use Yarn, running yarn --check-files usually fix that for me (also you may want to change Node to latest LTS)

@MoKhajavi75
Copy link
Author

@facebook-github-bot duplicate #19529

If you use Yarn, running yarn --check-files usually fix that for me (also you may want to change Node to latest LTS)

It's not duplicate because:

As mentioned here, this must be fixed

This bug is still in the 0.57.5 so i opened this issue!

@sabirbasha
Copy link

@facebook-github-bot duplicate #19529
If you use Yarn, running yarn --check-files usually fix that for me (also you may want to change Node to latest LTS)

It's not duplicate because:

As mentioned here, this must be fixed

This bug is still in the 0.57.5 so i opened this issue!

Still we are facing same issue in React 0.57.5..

@alvgaona
Copy link

alvgaona commented Nov 28, 2018

Same issue dragged from previous versions. After running #19529 workarounds and running react-native run-ios, config.h disappears from /src/base and app does not run. Still need to fix this.

@brascene
Copy link

Same issue here, experiencing it after ejecting the default created app with expo init. I guess would get the same issue with react-native init..

I've tried with ..\node_modules\react-native\third-party\glog-0.3.5
and when I run ./configure , I receive this error:
checking whether build environment is sane...
configure: error: unsafe absolute working directory name

Note, I'm using XCode 10.0, Legacy build system, RN 0.57.1, yarn 1.12.3

@alvgaona
Copy link

Same issue here, experiencing it after ejecting the default created app with expo init. I guess would get the same issue with react-native init..

I've tried with ..\node_modules\react-native\third-party\glog-0.3.5
and when I run ./configure , I receive this error:
checking whether build environment is sane...
configure: error: unsafe absolute working directory name

Note, I'm using XCode 10.0, Legacy build system, RN 0.57.1, yarn 1.12.3

My react-native info is the following.

  React Native Environment Info:
    System:
      OS: macOS 10.14.1
      CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
      Memory: 54.82 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 11.2.0 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    IDEs:
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.1 => 16.6.1 
      react-native: 0.57.7 => 0.57.7 
    npmGlobalPackages:
      react-native-cli: 2.0.1

I have been able to run ./configure and config.h appears in src folder. However, when running react-native run-ios all those files disappear.

@MoKhajavi75
Copy link
Author

Same issue here, experiencing it after ejecting the default created app with expo init. I guess would get the same issue with react-native init..

I've tried with ..\node_modules\react-native\third-party\glog-0.3.5
and when I run ./configure , I receive this error:
checking whether build environment is sane...
configure: error: unsafe absolute working directory name

Note, I'm using XCode 10.0, Legacy build system, RN 0.57.1, yarn 1.12.3

You can use ./configure and then make in the ..\node_modules\react-native\third-party\glog-0.3.5 folder and then clean your build folder from XCode as a temporary solution!

@kelset I think this is not fixed yet (despite of mentioned in the changelog)

@kelset
Copy link
Contributor

kelset commented Nov 28, 2018

The repro steps are really not clear, I don't understand what causes this issue.

@brascene
Copy link

I can confirm that with react-native init everything works well, the previous issue was there because the folder where the project was created, was in iCloud... and that messed up the relative paths, after I created project in another directory, no issues. Sorry for taking your time :)

@alvgaona
Copy link

I can confirm that with react-native init everything works well, the previous issue was there because the folder where the project was created, was in iCloud... and that messed up the relative paths, after I created project in another directory, no issues. Sorry for taking your time :)

Actually, react-native fails for me but expo init works like a charm.

@hramos
Copy link
Contributor

hramos commented Dec 14, 2018

@MohamadKh75 can you verify if 1/ this is still an issue on 0.58.0-rc.1, and 2/ if so, include a detailed list of steps to repro?

@hramos hramos changed the title 'config.h' file not found - mutex.h - 0.57.5 'config.h' file not found - mutex.h Dec 14, 2018
@MoKhajavi75
Copy link
Author

@hramos i'll reach my Mac in a week! Will do that as soon as i can!

@MoKhajavi75
Copy link
Author

@hramos i used 0.58.0-rc.1 and i can confirm that didn't get the error for 'config.h' file not found BUT i faced new issue.

I'll create a new issue for that!

@TRIPTI-JAIN
Copy link

In the Terminal, navigate to the react-native/third-party/glog folder inside node_modules (for me, this was cd node_modules/react-native/third-party/glog-0.3.4)
Once actively in this folder, run ../../scripts/ios-configure-glog.sh
Glog is configured and the required config.h header file is created for Xcode to find

@facebook facebook locked as resolved and limited conversation to collaborators Dec 19, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Dec 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

10 participants