Makefile 犯错误:“;生成[1]:***[目录]错误1“;
当我尝试以某种复杂性在makefile上运行“makeall”时,会出现以下错误:Makefile 犯错误:“;生成[1]:***[目录]错误1“;,makefile,gnu-make,Makefile,Gnu Make,当我尝试以某种复杂性在makefile上运行“makeall”时,会出现以下错误: C:\BITCLOUD\BitCloud_PS_SAM3S_EK_1_10_0\BitCloud_PS_SAM3S_EK_1_10_0\Applications\ZAppSi\Dem o\SEDevice>make all make -C makefiles/PC -f Makefile_PC_Gcc all APP_NAME=DemoSE make[1]: Entering directory 'C:/
C:\BITCLOUD\BitCloud_PS_SAM3S_EK_1_10_0\BitCloud_PS_SAM3S_EK_1_10_0\Applications\ZAppSi\Dem o\SEDevice>make all
make -C makefiles/PC -f Makefile_PC_Gcc all APP_NAME=DemoSE
make[1]: Entering directory
'C:/BITCLOUD/BitCloud_PS_SAM3S_EK_1_10_0/BitCloud_PS_SAM3S_EK_1_10_0/Applications/ZAppSi/Demo/SEDevice/makefiles/PC'
A sintaxe do comando está incorrecta.
make[1]: *** [directories] Error 1
make[1]: Leaving directory
'C:/BITCLOUD/BitCloud_PS_SAM3S_EK_1_10_0/BitCloud_PS_SAM3S_EK_1_10_0/Applications/ZAppSi/Demo/SEDevice/makefiles/PC'
make: *** [all] Error 2
线路在哪里
A sintaxe do comando está incorrecta.
翻译成英语的意思是:“命令的语法不正确”
我已经尝试将项目更改为不同的目录,检查文件名中的空格,使用gnumake,还使用mingwmake(mingw32-make),结果与“make”相同。我还检查了makefile中包含的所有文件,它们对应
我不是makefiles方面的专家,所以我请求帮助。
make抛出此类错误时出现的主要问题是什么?抛出此错误的可能不是
make
,而是make执行的命令返回非零退出状态,在这种情况下为状态1(由于错误1);然后顶级make
停止,出现错误2。请注意,默认情况下,make
在命令失败时立即停止。
由于输出没有显示执行了什么命令,因此无法准确地判断出发生了什么错误
编辑:从GNU制作手册:
我建议运行
make--debug=j
查看命令。引发此错误的可能不是make
,但make执行的命令返回非零退出状态,在这种情况下为状态1(由于错误1);然后顶级make
停止,出现错误2。请注意,默认情况下,make
在命令失败时立即停止。
由于输出没有显示执行了什么命令,因此无法准确地判断出发生了什么错误
编辑:从GNU制作手册:
我建议运行make--debug=j
查看命令。如何正确地“调试”makefile以查看是否有错误?有什么提示吗?我怎样才能正确地“调试”我的makefile以查看是否有问题?有什么提示吗?
-d Print debugging information in addition to normal processing.
The debugging information says which files are being considered
for remaking, which file-times are being compared and with what
results, which files actually need to be remade, which implicit
rules are considered and which are applied---everything inter‐
esting about how make decides what to do.
--debug[=FLAGS]
Print debugging information in addition to normal processing.
If the FLAGS are omitted, then the behavior is the same as if -d
was specified. FLAGS may be a for all debugging output (same as
using -d), b for basic debugging, v for more verbose basic
debugging, i for showing implicit rules, j for details on invo‐
cation of commands, and m for debugging while remaking make‐
files.