Page 1 of 1

make menuconfig fails

Posted: Sun Mar 26, 2017 5:23 pm
by johnabel
I just installed the ESP-IDE on Ubuntu, everything went fine but can't run make....
I googled about it and found some similar problems but no fix there worked for me.
Just a list of things I have already done:

1 - Install packages. Yes, I ran:

sudo apt-get install git wget make libncurses-dev flex bison gperf python python-serial

2 - export the path. I did:

export PATH=$PATH:$home/john/ESP/xtensa-esp32-elf/bin (as I put it there)

3 - Downloaded the ESP-IDF with the -recursive option.

4 - Exported the IDF path:

export IDF_PATH=/home/john/ESP/esp-idf

Nevertheless when I run make menuconfig in an example folder (hello_world moved to ESP), get this:

/home/john/ESP/esp-idf/make/common.mk:10: /home/john/ESP/hello_world/build/include/config/auto.conf: No such file or directory
make[1]: Entering directory '/home/john/ESP/esp-idf/tools/kconfig'
cc -D_GNU_SOURCE -DCURSES_LOC="<ncurses.h>" -DLOCALE -c -o mconf.o mconf.c
Assembler messages:
Fatal error: can't create mconf.o: Permission denied
<builtin>: recipe for target 'mconf.o' failed
make[1]: *** [mconf.o] Error 1
make[1]: Leaving directory '/home/john/ESP/esp-idf/tools/kconfig'
/home/john/ESP/esp-idf/make/project_config.mk:20: recipe for target '/home/john/ESP/esp-idf/tools/kconfig/conf' failed
make: *** [/home/john/ESP/esp-idf/tools/kconfig/conf] Error 2

Any ideas?

Re: make menuconfig fails

Posted: Sun Mar 26, 2017 11:07 pm
by ESP_Angus
Hi John,

The build system tries to create mconf.o in the esp-idf/tools/kconfig directory. Permission Denied implies that the user running "make" doesn't have permission to write this file in this directory.

Is it possible that you ran the "git clone" for IDF as root (ie with sudo) or as a different user to the one who is running "make menuconfig"? That would lead to your normal user not being able to write to this directory.

Angus

Re: make menuconfig fails

Posted: Tue Apr 04, 2017 7:49 pm
by johnabel
I managed to fix that, now I don't remember what the problem was but it could probably be because of folder ownership, thanks.