[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
다음은 make
에서 흔히 볼 수 있는 애러 메세지이다. 애러 메세지와
함께 그 애러메세지가 무슨 뜻인지, 그리고 어떻게 그 애러를 고칠 수
있는지에 대한 정보가 있다.
어떤 경우에 make
애러는 치명적인 문제가 아니다. 특히 명령어 줄의 앞에
-
를 붙인 경우, 혹은 -k
명령행 옵션을 사용한 경우는
그렇다. 치명적인 애러의 경우는 앞에 ***
가 붙는다.
Error messages are all either prefixed with the name of the program (usually `make'), or, if the error is found in a makefile, the name of the file and linenumber containing the problem.
In the table below, these common prefixes are left off.
These errors are not really make
errors at all. They mean that a
program that make
invoked as part of a command script returned a
non-0 error code (`Error NN'), which make
interprets
as failure, or it exited in some other abnormal fashion (with a
signal of some type).
If no ***
is attached to the message, then the subprocess failed
but the rule in the makefile was prefixed with the -
special
character, so make
ignored the error.
This is make
's generic "Huh?" error message. It means that
make
was completely unsuccessful at parsing this line of your
makefile. It basically means "syntax error".
One of the most common reasons for this message is that you (or perhaps your oh-so-helpful editor, as is the case with many MS-Windows editors) have attempted to indent your command scripts with spaces instead of a TAB character. Remember that every line in the command script must begin with a TAB character. Eight spaces do not count.
This means the first thing in the makefile seems to be part of a command
script: it begins with a TAB character and doesn't appear to be a legal
make
command (such as a variable assignment). Command scripts
must always be associated with a target.
The second form is generated if the line has a semicolon as the first
non-whitespace character; make
interprets this to mean you left
out the "target: dependency" section of a rule.
This means that make
decided it needed to build a target, but
then couldn't find any instructions in the makefile on how to do that,
either explicit or implicit (including in the default rules database).
If you want that file to be built, you will need to add a rule to your makefile describing how that target can be built. Other possible sources of this problem are typos in the makefile (if that filename is wrong) or a corrupted source tree (if that file is not supposed to be built, but rather only a dependency).
The former means that you didn't provide any targets to be built on the
command line, and make
couldn't find any makefiles to read in.
The latter means that some makefile was found, but it didn't contain any
default target and none was given on the command line. GNU make
has nothing to do in these situations.
A makefile specified on the command line (first form) or included (second form) was not found.
GNU make
allows commands to be specified only once per target
(except for double-colon rules). If you give commands for a target
which already has been defined to have commands, this warning is issued
and the second set of commands will overwrite the first set.
This means that make
detected a loop in the dependency graph:
after tracing the dependency yyy of target xxx, and its
dependencies, etc., one of them depended on xxx again.
This means you've defined a normal (recursive) make
variable
xxx that, when its expanded, will refer to itself (xxx).
This is not allowed; either use simply-expanded variables (:=
) or
use the append operator (+=
).
변수나 함수를 참조할 때 괄호나 중괄호를 닫는 걸 잊어버렸다.
이 함수에서 꼭 필요한 갯수의 인자를 쓰지 않았다. 인자에 대한 설명을 보려면 그 함수의 설명을 본다.
These are generated for malformed static pattern rules. The first means
there's no pattern in the target section of the rule, the second means
there are multiple patterns in the target section, and the third means
the target doesn't contain a pattern character (%
).
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Autobuild on March, 29 2007 using texi2html 1.76.