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

SDK Makefile versus root Makefile problem #85

Closed
jfbortolotti opened this issue Aug 29, 2015 · 6 comments
Closed

SDK Makefile versus root Makefile problem #85

jfbortolotti opened this issue Aug 29, 2015 · 6 comments

Comments

@jfbortolotti
Copy link

While willing to compile an examples in sdk/app, got the following error:
~/esp8266/esp-open-sdk/sdk/app$ make
../../Makefile:288: warning: overriding commands for target clean' ../Makefile:299: warning: ignoring old commands for targetclean'
You cloned without --recursive, fetching submodules for you.
git submodule update --init --recursive
make -C crosstool-NG -f ../Makefile _ct-ng
make: *** crosstool-NG: No such file or directory. Stop.
make: *** [crosstool-NG/ct-ng] Error 2

This seems to be due to the app Makefile including the ../../Makefile which is the one from root but with a different path, then trying to regenerate the crosstool-NG compile/install process.

Workaround found: rename esp-open-sdk/Makefile to something else(Makefile.old) and app compilation will work.

@me21
Copy link

me21 commented Sep 4, 2015

Or patch Makefile in the root of SDK to prevent it from including Makefile from parent dir.

@pfalcon
Copy link
Owner

pfalcon commented Sep 4, 2015

Or don't do anything is esp-open-sdk source tree, because it's all, well, esp-open-sdk source tree. Clone vendor sdk outside the tree and play with it there. Or report the issue to vendor, telling them not to include random makefiles outside their tree.

@pfalcon pfalcon closed this as completed Sep 4, 2015
@eku
Copy link

eku commented Sep 4, 2015

Well, I had the same problem. Renaming the files outside the vendor tree from Makefile to makefile did the trick.

@Scott--R
Copy link

Same issue for me. I spent 2 days frustrated by this error, and then stumbled onto this thread. No matter where I put the source code I always got this exact error. But the moment I renamed the Makefile in the root directory, it compiled perfectly. I will simply change the Makefile name back to normal to pull updates, but I am so glad I finally got it working.

@surak
Copy link

surak commented Jan 11, 2018

This error is caused by the BSD's "sed" utility. Try "brew install gnu-sed binutils"

@surak
Copy link

surak commented Jan 11, 2018

And wget, if you don't have it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants