eclipse无法运行kotlin（JDK 10）(eclipse cannot run kotlin (JDK 10))

 缺省情况下，bitbake.conf包含在运行时传递给make命令的EXTRA_OEMAKE =“-e MAKEFLAGS =”（请参阅​​运行$ {MAKE} $ {EXTRA_OEMAKE}“$ @”的base.bbclass）。 
 
 -e选项意味着环境变量会覆盖makefile（来自make --help）。 您还会注意到，bitbake.conf在其他几个导出的变量中设置了导出CFLAGS =“$ {TARGET_CFLAGS}”，因此在环境中设置了CFLAGS。 
 
 这样做的原因是有一些编译器标志在交叉编译时很重要，一般来说，系统比makefile有更好的使用方法。 这有时会失败，因为你发现。 
 
 你可以从EXTRA_OEMAKE中删除-e选项，但是你可能会冒其他关键变量设置不正确的风险（比如它是否会找到交叉编译器）。 另一个稍微干净的解决方案可能是添加到TARGET_CFLAGS，例如： 
 
 TARGET_CFLAGS + =“-Wall -std = gnu99” 
 
 不幸的是，这里可能没有完美的解决方案，但希望这有助于理解它为什么会这样做。 

By default, bitbake.conf contains EXTRA_OEMAKE = "-e MAKEFLAGS=" which is passed to the make command when its run (see base.bbclass, which runs ${MAKE} ${EXTRA_OEMAKE} "$@").
 
The -e option to make means that environment variables override makefiles (from make --help). You'll also notice that bitbake.conf sets export CFLAGS = "${TARGET_CFLAGS}" amongst several other exported variables, so CFLAGS is set in the environment.
 
The reason it does this is that there are some compiler flags which are important whilst cross compiling and in general, the system has a better idea of what to use than the makefile does. This does sometimes fail as you've found. 
 
You could remove the -e option from EXTRA_OEMAKE but you run the risk of other key variables not being set correct (e.g. would it find the cross compiler). Another slightly cleaner solution might be to add to TARGET_CFLAGS, e.g.:
 
TARGET_CFLAGS += "-Wall -std=gnu99"
 
Unfortunately there is likely no perfect solution here however hopefully this helps understand why it does what it does.