Compiling Make Error 126 Linux
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta
Make Error 126 Permission Denied
Discuss the workings and policies of this site About Us Learn gnu make error 2 more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us make error 2 linux Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like
Make All Error 2
you, helping each other. Join them; it only takes a minute: Sign up GNU Make Error 126, C:\Program is a directory up vote 1 down vote favorite 1 GNU make gives me a strange error message, which I do not understand. gao@L8470-130213 ~ $ make echo Test C:\Program: C:\Program: is a directory make: *** [test] Error 126
Make * * * Error 2
This is what I thought of verifying: gao@L8470-130213 ~ $ less makefile test: echo Test gao@L8470-130213 ~ $ which make /c/Programx86/GnuWin32/bin/make gao@L8470-130213 ~ $ /c/Progra~2/GnuWin32/bin/make.exe test echo Test C:\Program: C:\Program: is a directory make: *** [test] Error 126 gao@L8470-130213 ~ $ make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-pc-mingw32 It feels like some other program is trying to run at the end, and that its path includes some spaces. In that case, what program could it be, and how can I prevent it from running? I have seen this thread and tried to disable my antivirus, which did not help. I have also looked into permissions, but I am not sure if makefile needs execution rights. I can't seem to be able to change that anyway (running in bash on windows. makefile is not read
board.Please contact the Board Administrator for https://root.cern.ch/phpBB3/viewtopic.php?t=19582 more information.A ban has been issued on your IP address. Board index All times are UTC+02:00 Delete all board cookies The team Contact us Powered by phpBB Forum Software © phpBB LimitedSE Square Left by PhpBB3 BBCodes
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 http://superuser.com/questions/772891/xsum-permission-denied-make-xsum-out-error-126 Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer https://www.gnu.org/s/make/manual/html_node/Error-Messages.html enthusiasts and power users. 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 error 2 top ./xsum: Permission denied make: *** [xsum.out] Error 126 up vote 0 down vote favorite I am trying to insall f2c/f77 compiler on mac osx using the instructions given http://www.webmo.net/support/fortran_osx.html and I get the following error : ./xsum: Permission denied make: *** [xsum.out] Error 126 please help , as in installation it misses to create : /usr/local/bin/f2c the install_f2c_osx.csh contains: #! /bin/csh #! /bin/csh setenv INSTALL /usr/local curl "http://netlib.sandia.gov/cgi-bin/netlib/netlibfiles.tar?filename=netlib/f2c" -o "f2c.tar" make error 1 tar -xvf f2c.tar gunzip -rf f2c/* cd f2c mkdir libf2c mv libf2c.zip libf2c cd libf2c unzip libf2c.zip cp makefile.u Makefile make cp f2c.h $INSTALL/include cp libf2c.a $INSTALL/lib cd ../src cp makefile.u Makefile make cp f2c $INSTALL/bin cd .. mkdir -p $INSTALL/share/man/man1 cp f2c.1t $INSTALL/share/man/man1 cp fc $INSTALL/bin/f77 chmod +x $INSTALL/bin/f77 cd .. rm -rf f2c echo "==================SUMMARY==================" echo $0 " has built and installed:" find $INSTALL -name '*f2c*' -mmin -5 find $INSTALL -name '*f77*' -mmin -5 osx permissions makefile share|improve this question edited Jun 25 '14 at 5:40 asked Jun 24 '14 at 16:32 user2721585 14 What command do you run that produces this output? –Michael Kjörling Jun 24 '14 at 16:38 after downloading the .csh file from the site : –user2721585 Jun 25 '14 at 5:31 'code'$ chmod +x install_f2c_osx.csh $ sudo ./install_f2c_osx.csh –user2721585 Jun 25 '14 at 5:31 @MichaelKjörling –user2721585 Jun 26 '14 at 10:37 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote I've just come across this issue myself (on CentOS 6.5), but managed to fix it by adding a 'chmod' in the installation script at line 6. See the revised scripts below. I've included fixed version of both the Linux and MacOSX
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 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 line number containing the problem. In the table below, these 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 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 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