Gnu Make Error 57
Contents |
to fix them. Sometimes make errors are not fatal, especially in the presence of a - prefix on a recipe line, or the -k command line option. Errors that are fatal are prefixed with the string ***. Error make error codes messages are all either prefixed with the name of the program (usually ‘make’), or, if makefile error 2 the error is found in a makefile, the name of the file and line number containing the problem. In the table below, these make all error 2 common prefixes are left off. ‘[foo] Error NN’ ‘[foo] signal description’ These errors are not really make errors at all. They mean that a program that make invoked as part of a recipe returned a non-0 error code (‘Error
Make * * * Error 2
NN’), which make interprets as failure, or it exited in some other abnormal fashion (with a signal of some type). See Errors in Recipes. If no *** is attached to the message, then the sub-process failed but the rule in the makefile was prefixed with the - special character, so make ignored the error. ‘missing separator. Stop.’ ‘missing separator (did you mean TAB instead of 8 spaces?). Stop.’ This means that make could not understand much of linux make error 2 anything about the makefile line it just read. GNU make looks for various separators (:, =, recipe prefix characters, etc.) to indicate what kind of line it’s parsing. This message means it couldn’t find a valid one. 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 recipe lines with spaces instead of a tab character. In this case, make will use the second form of the error above. Remember that every line in the recipe must begin with a tab character (unless you set .RECIPEPREFIX; see Special Variables). Eight spaces do not count. See Rule Syntax. ‘recipe commences before first target. Stop.’ ‘missing rule before recipe. Stop.’ This means the first thing in the makefile seems to be part of a recipe: it begins with a recipe prefix character and doesn’t appear to be a legal make directive (such as a variable assignment). Recipes 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: prerequisite" section of a rule. See Rule Syntax. ‘No rule to make target `xxx'.’ ‘No rule to make target `xxx', needed by `yyy'.’ This means that make decided it needed
%% "Chris Jimison"
writes: cj> I keep getting a make error "Error 255". I would like to makefile error 1 know cj> what an "Error 255" is. I justGcc Error 2
need to know where I can find a cj> list of all the make error
Gcc Error 1
codes. I have look all over and can't cj> find a list of all the possible make errors. Any help would be cj> most appreciated. https://www.gnu.org/s/make/manual/html_node/Error-Messages.html The error messages that GNU make can generate are listed in the GNU make manual, in the section titled Error Messages. GNU make does not generate "error codes"; the above message means that the program that GNU make invoked to update a target exited with a non-0 exit code (in https://lists.gnu.org/archive/html/help-make/2002-12/msg00040.html this case, exit code 255, or -1). GNU make determines whether or not a command succeeds be examining the exit code: as per all UNIX operations an exit code of 0 means success, any other code means failure. You need to look at the messages generated before this one to find out why the command you invoked did not work. In short, this is not a GNU make problem at all. -- ------------------------------------------------------------------------------- Paul D. Smith
Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist reply via email to [Prev in Thread] Current Thread [Next in Thread] Make error code listing, Chris Jimison, 2002/12/26 Re: Make error code listing, Paul D. Smith<= Prev by Date: Make error code listing Next by Date: Re: URGENT Previous by thread: Make error code listing Index(es): Date Threadcodes can’t occur on GNU systems, but they can occur using the GNU C Library on other systems. Macro: int EPERM Operation not permitted; only the owner of the file (or other resource) or processes http://www.gnu.org/s/libc/manual/html_node/Error-Codes.html with special privileges can perform the operation. Macro: int ENOENT No such file or directory. This is a “file doesn’t exist” error for ordinary files that are referenced in contexts where they are expected to already exist. Macro: int ESRCH No process matches the specified process ID. Macro: int EINTR Interrupted function call; an asynchronous signal occurred and prevented completion of the call. When this happens, you should try the call again. error 2 You can choose to have functions resume after a signal that is handled, rather than failing with EINTR; see Interrupted Primitives. Macro: int EIO Input/output error; usually used for physical read or write errors. Macro: int ENXIO No such device or address. The system tried to use the device represented by a file you specified, and it couldn’t find the device. This can mean that the device file was installed incorrectly, or gnu make error that the physical device is missing or not correctly attached to the computer. Macro: int E2BIG Argument list too long; used when the arguments passed to a new program being executed with one of the exec functions (see Executing a File) occupy too much memory space. This condition never arises on GNU/Hurd systems. Macro: int ENOEXEC Invalid executable file format. This condition is detected by the exec functions; see Executing a File. Macro: int EBADF Bad file descriptor; for example, I/O on a descriptor that has been closed or reading from a descriptor open only for writing (or vice versa). Macro: int ECHILD There are no child processes. This error happens on operations that are supposed to manipulate child processes, when there aren’t any processes to manipulate. Macro: int EDEADLK Deadlock avoided; allocating a system resource would have resulted in a deadlock situation. The system does not guarantee that it will notice all such situations. This error means you got lucky and the system noticed; it might just hang. See File Locks, for an example. Macro: int ENOMEM No memory available. The system cannot allocate more virtual memory because its capacity is full. Macro: int EACCES Permission denied; the file permissions do not allow the attempted operation. Macro: int EFAULT Bad address; an invalid point