I have a file called
commanKT and want to run it in a Linux terminal. Can someone help by giving the command to run this file? I tried
./commonRT but I'm getting the error:
Easier way to extract.SAR and.CAR files with SAPCAR under Windows April 12, 2012. This gives you an opportunity to see the messages output by sapcar.exe.
To execute a binary, use:
If you get an error:
bash: ./binary_name: cannot execute binary file
it'll be because it was compiled using a tool chain that was for a different target to that which you're attempting to run the binary on.
For example, if you compile 'binary_name.c' with
arm-none-linux-gnueabi-gcc and try run the generated binary on an x86 machine, you will get the aforementioned error.
To execute a binary or .run file in Linux from the shell, use the dot forward slash friend
and if it fails say because of permissions, you could try this before executing it
Hope it helps
:-) If not typo, why are you using
./commonRT instead of
Mar 17, 2013 - NSFWgaming is for mature audiences 18 years of age or older. For playable flash games, include '*[WEBGAME] *' in the title. Nsfw flash games reddit.
It is possible that you compiled your binary with incompatible architecture settings on your build host vs. your execution host.Can you please have a look at the enabled target settings via
on your build host? In particular, the
COLLECT_GCC_OPTIONS variable may give you valuable debug info. Then have a look at the CPU capabilities on your execution host via
Look out for mismatches such as
-msse4.2 [enabled] on your build host but a missing
sse4_2 flag in the CPU capabilities.
If that doesn't help, please provide the output of
ldd commonKT on both build and execution host.
This is an answer to @craq : Quicken 2018 mac torrent.
I just compiled the file from C source and set it to be executable with chmod. There were no warning or error messages from gcc.
I'm a bit surprised that you had to 'set it to executable' -- my
gcc always sets the executable flag itself. This suggests to me that
gcc didn't expect this to be the final executable file, or that it didn't expect it to be executable on this system.
Now I've tried to just create the object file, like so:
hello.c is a typical 'Hello World' program.) But my error message is a bit different:
On the other hand, this way, the output of the
file command is identical to yours:
Whereas if I compile correctly, its output is much longer.
What I am saying is: I suspect it has something to do with the way you compile and link your code. Maybe you can shed some light on how you do that?
The only way that works for me (extracted from here):
Then run it by writing
If you get a permission error you might have to launch your application with root privileges:
Or, the file is of a filetype and/or architecture that you just cannot run with your hardware and/or there is also no fallback binfmt_misc entry to handle the particular format in some other way. Use
file(1) to determine.
your compilation option -c makes your compiling just compilation and assembly, but no link.
If it is not a typo, as pointed out earlier, it could be wrong compiler options like compiling 64 bit under 32 bit. It must not be a toolchain.
full path for binary file. For example: /home/vitaliy2034/binary_file_name. Oruse directive './+binary_file_name'.'./' in unix system it return full path to directory, in which you open terminal(shell).I hope it helps.Sorry, for my english language)
Not the answer you're looking for? Browse other questions tagged linuxbash or ask your own question.
I am new to Linux.I am currently trying to write a command line which should execute a *.exe inside a folder abc.
I have tried
But the error says
no such file or directory.
migrated from stackoverflow.comSep 29 '09 at 22:24
This question came from our site for professional and enthusiast programmers.
How To Install Linux Os
but if it's really a Windows program, you will need to install 'wine', then do:
but only some Windows programs will work under wine.
This anwswer is combining other answers in to this question into one.
The info.exe file will either execute under Linux or Windows, but not both.
If the file is a windows file, it will not run under Linux on it's own. So if that's the case, you could try running it under a windows emulator (WINE). If it's not compatible with wine, then you won't be able to execute it under Linux.
Before you can start, you will need to install wine. The steps you need to install wine will vary on the linux platform you are on. You can probably google 'Ubuntu install wine', if for example, you're installing ubuntu.
Once you have wine installed, then you'd be able to execute these commands.
if you know this file to run under linux, then you'll want to execute these commands:
Change to your abc directory
Then you'll want to change permissions to allow all users to execute this file (a+x).
you could also allow just the user to execute (u+x)
Launch the program, the ./ tells the command line to look in the current pathfor the file to execute (if the 'current' directory isn't in the $PATH environmentvariable.
you can't :) exe is Microsoft only. now if you had a linux executable you could do:
On Linux you give the file executable permissions. It isn't the extension that determines whether or not it can be executed (as on windows.)
Assuming you have a valid file that can be executed in Linux, (not a windows/dos file) do this:
Note that you need the leading ./ for the shell to find the file in the current directory!
This really belongs on superuser though.
I recently wanted to run some old MSDOS .exe files and I could just use dosbox. On Ubuntu it was just
How To Install Linux System
apt-get install dosbox
.exes are generally Windows executables, not linux ones. To run those, use something like WINE.
Otherwise, to run a Linux executable, there are many ways, e.g.:
- cd abc; ./info.exe
- Add 'abc' to your PATH, then just run it as a normal command..
Wine is a program that you can install, it's a program to run .exe files in linux.
apt-get install wine
(go to teh directory of your file: /cd (ex: Desktop/)And to open your .exe file:
wine PROGRAM [AGRUMENTS]
Any problems with wine you can do: wine --help
That's the way I tried and it works.