ESP8266 Community Forum

- Tue May 24, 2016 9:53 am #47939 I'm using default tool chain coming with Arch Linux on raspberry Pi.

CC is set to $(XTENSA_TOOLS_ROOT)$(TOOLPREFIX)gcc in libesphttpd Makefile.
When calling mkespfsimage Makefile, it will also use this CC variable which is set to xtensa toolchain.

So passing CC=$(HOSTCC) when calling mkespfsimage Makefile should fix the issue.

But I don't understand why I'm the only one to have the issue. It could be an environment issue.

Anyway, please let me know if you want me to upload a patch for this. I would be pleased to help.

- Wed May 25, 2016 2:00 am #47986

I'm using default tool chain coming with Arch Linux on raspberry Pi.

CC is set to $(XTENSA_TOOLS_ROOT)$(TOOLPREFIX)gcc in libesphttpd Makefile.
When calling mkespfsimage Makefile, it will also use this CC variable which is set to xtensa toolchain.

So passing CC=$(HOSTCC) when calling mkespfsimage Makefile should fix the issue.

But I don't understand why I'm the only one to have the issue. It could be an environment issue.

Anyway, please let me know if you want me to upload a patch for this. I would be pleased to help.

Then that is your problem. Libesphttpd expects CC to be set to the host CC, it takes care of setting CC for the target itself. As far as I am aware (bit I could be wrong here), most of the ESP8266 frameworks/projects don't require CC to be set to the Xtensa tools either, so I suggest to get those definitions of CC out of your environment.