Make error 127 linux

make: *** [cmake_check_build_system] Error 127

I have a computer installed with Ubuntu 18.04. I tried to use the command «make» for the star-engine. https://gitlab.com/meso-star/star-engine However, the following errors pop up:

make: /snap/cmake/283/bin/cmake: Command not found Makefile:384: recipe for target 'cmake_check_build_system' failed make: *** [cmake_check_build_system] Error 127 

I tried removing «cmake» and install it again. But the problem persists. I think the problem is due to unknown changes to the computer by ubuntu’s updates during these 2 weeks. Thank you very much

So did you delete the Makefile, and regenerate it by running the cmake command in the instructions?

Running make clean does not delete the Makefile. You need to manually delete the Makefile. Also, it is important to run the CMake command before running make , because CMake regenerates the Makefile.

Thank you very much. I can now run star-engine. But I have another problem that is I have a foler pt/build , I tried to run make and the following error pop up CMakeFiles/pt.dir/build.make:62: recipe for target ‘CMakeFiles/pt.dir/home/kenchung/pt_ken/src/pt.c.o’ failed make[2]: *** [CMakeFiles/pt.dir/home/kenchung/pt_ken/src/pt.c.o] Error 1 CMakeFiles/Makefile2:67: recipe for target ‘CMakeFiles/pt.dir/all’ failed make[1]: *** [CMakeFiles/pt.dir/all] Error 2 Makefile:83: recipe for target ‘all’ failed make: *** [all] Error 2

This Q&A appears to be the same issue mentioned in your question post. CMake is not found when running through make

Источник

How to fix Make error 127?

Terminals are very powerful, regardless of what operating system you’re using. This means that while you can perform just about any OS task with a few commands, you need to know these commands to take advantage of them. Of course, different operating systems use different languages in their terminals as well, meaning you need to decide to have mastery over one or use multiple.

In this article, we’re talking about Make error 127, its causes and what you can do to fix the problem.

What causes Make error 127?

The Make error 127 generally occurs when you’re working with a Go operator-sdk project cloned from Github as the command doesn’t generate the bin directory with the required files to run the Make installation.

As for code 127, it simply indicates a “command not found” error. Since the initial command hasn’t generated the files required, the Make installation fails as the system can’t find the source files to run or read the command.

How to fix Make error 127?

Depending on what’s causing your error, here are two fixes you can try out.

Reinstall a different version of the Operator-SDK

First up, if the problem is being caused by operator-sdk, we can try either rolling back to version 18.0.0 or pushing forward to the latest version available (assuming the latest version has fixed the bug.

All you have to do is uninstall operator-sdk using brew or apt-get or whatever package manager you’re using. Once that’s done, we reinstall a different version (either version 18.0.0 or the latest one) as well as the latest version of Go. Keep in mind that if you’re using version 18.0.0 of operator-sdk, we recommend installing version 1.17.6 of Go.

Finally, check if the bin folder has now been created and if it has, you can go ahead and run your Make installation without any errors.

Check your PATH variables

Since error 127 also indicates that a command or file required to run a command is missing, try checking your PATH variable to see if the command exists there. Alternatively, a simpler way of doing this is opening a terminal in the root directory of whatever command you want to run and then run the problematic command.

Yadullah Abidi

Yadullah is a Computer Science graduate who writes/edits/shoots/codes all things cybersecurity, gaming, and tech hardware. When he’s not, he streams himself racing virtual cars. He’s been writing and reporting on tech and cybersecurity with websites like Candid.Technology and MakeUseOf since 2018. You can contact him here: [email protected]

Источник

Eclipse Make Error 127

this is my first time using Eclipse, and my first time programming in a linux environment. So I might end up posting some semi-usless information, but I’m just trying to give what ever details I can. The Issue: I’m trying to build a project, and I’m getting the following errors and warnings. The Question: What would I have to do, and or get, in order to start working with c++ in linux, within an IDE? Fixing the error would be great, but the above stated is my underlying goal. IDE Info:

Eclipse Version: Helios Release Build id: 20100617-1415 

make: *** [src/xoorMath.o] Error 127 xoorMath C/C++ Problem 

Error launching external scanner info generator (g++ -E -P -v -dD /home/xoorath/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.cpp) xoorMath Unknown C/C++ Problem Error launching external scanner info generator (g++ -E -P -v -dD /home/xoorath/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.cpp) xoorMath Unknown C/C++ Problem 

//============================================================================ // Name : xoorMath.cpp // Author : // Version : // Copyright : Your copyright notice // Description : Hello World in C++, Ansi-style //============================================================================ #include using namespace std; int main() < cout 

################################################################################ # Automatically-generated file. Do not edit! ################################################################################ -include ../makefile.init RM := rm -rf # All of the sources participating in the build are defined here -include sources.mk -include subdir.mk -include src/subdir.mk -include objects.mk ifneq ($(MAKECMDGOALS),clean) ifneq ($(strip $(C++_DEPS)),) -include $(C++_DEPS) endif ifneq ($(strip $(C_DEPS)),) -include $(C_DEPS) endif ifneq ($(strip $(CC_DEPS)),) -include $(CC_DEPS) endif ifneq ($(strip $(CPP_DEPS)),) -include $(CPP_DEPS) endif ifneq ($(strip $(CXX_DEPS)),) -include $(CXX_DEPS) endif ifneq ($(strip $(C_UPPER_DEPS)),) -include $(C_UPPER_DEPS) endif endif -include ../makefile.defs # Add inputs and outputs from these tool invocations to the build variables # All Target all: xoorMath # Tool invocations xoorMath: $(OBJS) $(USER_OBJS) @echo 'Building target: $@' @echo 'Invoking: GCC C++ Linker' g++ -o"xoorMath" $(OBJS) $(USER_OBJS) $(LIBS) @echo 'Finished building target: $@' @echo ' ' # Other Targets clean: -$(RM) $(OBJS)$(C++_DEPS)$(C_DEPS)$(CC_DEPS)$(CPP_DEPS)$(EXECUTABLES)$(CXX_DEPS)$(C_UPPER_DEPS) xoorMath -@echo ' ' .PHONY: all clean dependents .SECONDARY: -include ../makefile.targets 

EDIT Tried running 'gcc -E -P -v -dD /home/xoorath/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.cpp'

[root@wt227-09-fedora xoorath]# gcc -E -P -v -dD /home/xoorath/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.cpp Using built-in specs. Target: i686-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch=i686 --build=i686-redhat-linux Thread model: posix gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) COLLECT_GCC_OPTIONS='-E' '-P' '-v' '-dD' '-mtune=generic' '-march=i686' cc1plus -E -quiet -v -P -D_GNU_SOURCE /home/xoorath/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.cpp -mtune=generic -march=i686 -dD gcc: error trying to exec 'cc1plus': execvp: No such file or directory [root@wt227-09-fedora xoorath]# 

Источник

Make linux ошибка 127

This semester I got this new subject where we get to work with Discovery STM32 F4, and we are still in the phase of setting it up. But I have this problem in the beginning.

When I try to compile this «blink» code I get this error:

So, as I got it so far, we are using this shortcut command «make» to compile code, and we were given instruction to set it up as it’s shown in images below:

Can anyone see what’s the problem here?

19.6k 6 gold badges 35 silver badges 65 bronze badges

Error 127 means one of two things:

1. file not found: the path you’re using is incorrect. double check that the program is actually in your $PATH , or in this case, the relative path is correct — remember that the current working directory for a random terminal might not be the same for the IDE you’re using. it might be better to just use an absolute path instead.
2. ldso is not found: you’re using a pre-compiled binary and it wants an interpreter that isn’t on your system. maybe you’re using an x86_64 (64-bit) distro, but the prebuilt is for x86 (32-bit). you can determine whether this is the answer by opening a terminal and attempting to execute it directly. or by running file -L on /bin/sh (to get your default/native format) and on the compiler itself (to see what format it is).

if the problem is (2), then you can solve it in a few diff ways:

1. get a better binary. talk to the vendor that gave you the toolchain and ask them for one that doesn’t suck.
2. see if your distro can install the multilib set of files. most x86_64 64-bit distros allow you to install x86 32-bit libraries in parallel.
3. build your own cross-compiler using something like crosstool-ng.
4. you could switch between an x86_64 & x86 install, but that seems a bit drastic ;).

answered Apr 2, 2016 at 1:02

Mike Frysinger Mike Frysinger

2,799 1 gold badge 21 silver badges 26 bronze badges

I am trying to install shc on Ubuntu 18.04

wget http://www.datsi.fi.upm.es/~frosal/sources/shc-3.8.9b.tgz tar xvfz shc-3.8.9.tgz cd shc-3.8.9 make 

But receive the following error:

cc -Wall shc.c -o shc make: cc: Command not found makefile:31: recipe for target 'shc' failed make: *** [shc] Error 127 

# Makefile # INSTALL_PATH = /usr/local # For SCO CFLAGS = -b elf -O -D_SVID # For IRIX CFLAGS = -xansi -fullwarn -O3 -g0 # For Solaris CFLAGS = -fast -xO4 -s -v -Xa # For HPUX CFLAGS = -Wall -O -Ae # For OSF1 CFLAGS = -w -verbose -fast -std1 -g0 # For GNU C compiler CFLAGS = -Wall # -O6 -pedantic #SHELL = /bin/sh SHCFLAGS = -v -T # Add -T option to allow binary to be traceable all: shc ask_for_test shc: shc.c $(CC) $(CFLAGS) $@.c -o $@ ask_for_test: @echo '*** �Do you want to probe shc with a test script?' @echo '*** Please try. make test' test: make_the_test ask_for_strings make_the_test: match.x @echo '*** Running a compiled test script!' @echo '*** It must show files with substring "sh" in your PATH. ' ./match.x sh match.x: shc match @echo '*** Compiling script "match"' CFLAGS="$(CFLAGS)" ./shc $(SHCFLAGS) -f match ask_for_strings: @echo '*** �Do you want to see strings in the generated binary?' @echo '*** Please try. make strings' strings: make_the_strings ask_for_expiration make_the_strings: match.x @echo '*** Running: "strings -n 5 'match.x'"' @echo '*** It must show no sensible information. ' strings -n 5 match.x ask_for_expiration: @echo '*** �Do you want to probe expiration date?' @echo '*** Please try. make expiration' expiration: til_yesterday ask_for_install til_yesterday: shc match @echo '*** Compiling "match" to expired date' CFLAGS="$(CFLAGS)" ./shc $(SHCFLAGS) -vv -e `date "+%d/%m/%Y"` -f match @echo '*** Running a compiled test script!' @echo '*** It must fail showing "./match.x: has expired!"' ./match.x ask_for_install: @echo '*** �Do you want to install shc?' @echo '*** Please try. make install' install: shc @echo '*** Installing shc and shc.1 on '$(INSTALL_PATH) @echo -n '*** �Do you want to continue? '; read ANS; case "$$ANS" in y|Y|yes|Yes|YES) ;; *) exit 1;; esac; install -c -s shc $(INSTALL_PATH)/bin/ install -c -m 644 shc.1 $(INSTALL_PATH)/man/man1/ clean: rm -f *.o *~ *.x.c cleanall: clean rm -f shc *.x 

I have no idea how to fix this error. Can anyone help?

3,767 9 gold badges 30 silver badges 65 bronze badges

Источник