Gnu Make Error 1
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business make error codes Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation
Gcc Error 1
Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like
Makefile Error 2
you, helping each other. Join them; it only takes a minute: Sign up make: *** [ ] Error 1 error up vote 17 down vote favorite 4 I am trying to compile a Pro*C file on gcc
Makefile Error 1
and I am getting this error : make: *** [MedLib_x.o] Error 1 This is the command printed by make: /usr/bin/gcc -g -fPIC -m64 -DSS_64BIT_SERVER -I/home/med/src/common - I/u01/app/oradb11r2/product/11.2.0/dbhome_3/rdbms/demo -I/u01/app/oradb11r2/product/11.2.0/dbhome_3/rdbms/public -I/u01/app/oradb11r2/product/11.2.0/dbhome_3/precomp/public -I/u01/app/oradb11r2/product/11.2.0/dbhome_3/xdk/include INCLUDE=/u01/app/oradb11r2/product/11.2.0/dbhome_3/precomp/public -lnapi -ltabs -c MedLib_x.c Please help me why this make error is coming? Although object file is also created. gcc makefile share|improve this question edited Apr 4 '11 at 7:31 asked Apr 4 '11 at 7:10 QMG 1492213 Without more details from the linux make error 1 error message it is difficult to know what is wrong –fnokke Apr 4 '11 at 7:13 The error that you've quoted must have been preceded by an error from GCC, please quote that as well. –DarkDust Apr 4 '11 at 7:16 Thank you for reply. What more details you require, please explain? –QMG Apr 4 '11 at 7:32 add a comment| 4 Answers 4 active oldest votes up vote 16 down vote From GNU Make error appendix, as you see this is not a Make error but an error coming from gcc. ‘[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 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 subprocess failed but the rule in the makefile was prefixed with the - special character, so make ignored the error. So in order to attack the problem, the error message from gcc is required. Paste the command in the Makefile directly to the command line and see what gcc says. For more details on Make errors click here. share|improve th
in the recipe is executed in a new shell; after the last line is finished, the rule is finished. If there is an error (the exit status is nonzero), make gives up make * * * error 1 c++ on the current rule, and perhaps on all rules. Sometimes the failure of gcc error 2 a certain recipe line does not indicate a problem. For example, you may use the mkdir command to ensure that make error 2 a directory exists. If the directory already exists, mkdir will report an error, but you probably want make to continue regardless. To ignore errors in a recipe line, write a ‘-’ at the http://stackoverflow.com/questions/5535548/make-error-1-error beginning of the line’s text (after the initial tab). The ‘-’ is discarded before the line is passed to the shell for execution. For example, clean: -rm -f *.o This causes make to continue even if rm is unable to remove a file. When you run make with the ‘-i’ or ‘--ignore-errors’ flag, errors are ignored in all recipes of all rules. A rule in the makefile https://www.gnu.org/s/make/manual/html_node/Errors.html for the special target .IGNORE has the same effect, if there are no prerequisites. These ways of ignoring errors are obsolete because ‘-’ is more flexible. When errors are to be ignored, because of either a ‘-’ or the ‘-i’ flag, make treats an error return just like success, except that it prints out a message that tells you the status code the shell exited with, and says that the error has been ignored. When an error happens that make has not been told to ignore, it implies that the current target cannot be correctly remade, and neither can any other that depends on it either directly or indirectly. No further recipes will be executed for these targets, since their preconditions have not been achieved. Normally make gives up immediately in this circumstance, returning a nonzero status. However, if the ‘-k’ or ‘--keep-going’ flag is specified, make continues to consider the other prerequisites of the pending targets, remaking them if necessary, before it gives up and returns nonzero status. For example, after an error in compiling one object file, ‘make -k’ will continue compiling other object files even though it already knows that linking them will be im
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About http://unix.stackexchange.com/questions/18807/where-can-i-find-a-list-of-make-error-codes Us Learn more about Stack Overflow the company Business Learn more about hiring http://askubuntu.com/questions/620182/error-when-using-command-make developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask error 1 a question Anybody can answer The best answers are voted up and rise to the top Where can I find a list of 'make' error codes? up vote 14 down vote favorite 5 I am trying to compile a program written in Fortran using make (I have a Makefile and, while in the directory containing the Makefile, I type the command $ make target, where "target" is a make error 1 system-specific target specification is present in my Makefile. As I experiment with various revisions of my target specification, I often get a variety of error messages when attempting to call make. To give a few examples: make[1]: Entering directory /bin/sh: line 0: test: too many arguments ./dpp angfrc.f > angfrc.tmp.f /bin/sh: ./dpp: Permission denied make[1]: *** [angfrc.o] Error 126 make[1]: Leaving directory make: *** [cmu60] Error 2 and make[1]: Entering directory /bin/sh: line 0: test: too many arguments ./dpp -DSTRESS -DMPI -P -D'pointer=integer'-I/opt/mpich_intel/include angfrc.f > angfrc.tmp.f /bin/sh: ./dpp: Permission denied make[1]: *** [angfrc.o] Error 126 make[1]: Leaving directory make: *** [mpich-c2] Error 2 and make[1]: Entering directory /bin/sh: line 0: test: too many arguments ./dpp -DSTRESS -DMPI -P -D'pointer=integer' -I/opt/mpich_intel/include angfrc.f > angfrc.tmp.f /bin/sh: ./dpp: Permission denied make[1]: *** [angfrc.o] Error 126 make[1]: Leaving directory make: *** [mpi-intel] Error 2 Do you know how I can find a list of what the error codes, such as "Error 126" and "Error 2," mean? I found this thread on another website, but I am not sure what the reply means. Does it mean that there is no system-independent meaning of the make error codes? Can you please help me? Thank you. make error-handl
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error when using command 'make' up vote 0 down vote favorite I get error whenever I'm trying to 'make' file, I did this before I typed 'make': tar xjf xarchiver-0.5.4.tar.bz2 cd ./xarchiver-0.5.4 ./configure Configure command: thomas@thomas-pc:~/Downloads/xarchiver-0.5.4$ ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g...