Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Many thanks.
Chrism,
Where is that file, as I get this?
[root@CentOS65x64 /]# ls -l epel*.repo
ls: cannot access epel*.repo: No such file or directory
You have been registered on this forum for 5 years and apparently you have not taught yourself much about linux in that time. Members of this community are ready to offer help to anyone, but a couple of guidelines for getting useful help might be in order.
1. Make an effort to solve the problem yourself first. You can find many answers by doing a simple search on the internet and following/trying the solutions suggested there.
2. Educate yourself, search for answers, learn the basics of what you are doing, then ask reasonable questions that others can understand. Reasonable questions include enough information about your system, what has already been tried, and exactly what the goal is so that readers who offer help can tell if their answers are even in the correct ballpark to answer your real question.
FYI
One of the things that will quickly turn me personally against helping anybody is lack of effort. That you have been a registered member of this community for 5 years is good. However, that you asked an identical question 4 years ago and did not learn from that, that you have not even learned enough about running a system to know the location of the *.repo files on your system, that you are running the commands that you quoted as root (system administrator/super user) but do not understand the basics of how to locate and install software, that you apparently have made no effort to locate a program written for linux that will do what you want but instead are trying to install a windows program on linux, all combine to tell me you are someone who wants to be told in microscopic detail how and to have your hand held as you do your job.
As has already been stated, team viewer is readily available for linux, yet you apparently did not take any effort to locate that and instead asked a very vague generic question here about running a *.exe file on linux when you could have answered your own question in 2 minutes or less.
I can suggest that learning a little bit about the package manager for your system (yum, dnf, apt-get, etc) then using that to locate software you need and install dependencies at the same time as the main package will make your overall job easier.
You are logged in and operating as root, yet you use sudo????
How little you understand linux and its' various commands!!
Please learn what you are doing!!
Users should NEVER do day-to-day operations when logged in as root. As root a simple typo such as "rm -rf / home/user/directoryname" can erase the entire system from your drive.
what to run next, to enable to run Windows .exe file?
As you've been told/asked before:
You asked this same question FOUR YEARS AGO...the same answer(s) still apply.
You *MAY* be able to run your program with Wine, but you STILL HAVEN'T BOTHERED to tell us what this program actually is, despite being asked.
You've been told TWICE how to enable the EPEL repository..neither have mentioned the "yum-plugin-priorities" command.
You've been asked if there is a Linux equivalent to your program...and you've not answered.
If you're not going to show effort of your own, answer questions when asked, or even follow the suggestions when asked, there isn't much point in posting.
John,
I did run 'yum install yum-plugin-priorities' but what should be the next step to enable the execution of any .exe file (that is generated by Visual studio)?
John,
I did run 'yum install yum-plugin-priorities' but what should be the next step to enable the execution of any .exe file (that is generated by Visual studio)?
Sorry, but are you intentionally ignoring ALL the other posts in this thread, and not re-reading the OTHER thread you opened for the same question four years ago????
AGAIN: Install/run Wine. Your program MAY work and it may not. Wine is NOT windows...you STILL don't answer any questions about your application, seem to have ignored the advice about enabling the EPEL repository, and are asking AGAIN about this plugin-priorities command that NO ONE TOLD YOU TO RUN.
Can't be much more clear/plain/simple: install Wine and it may work. Answer questions about your application, and we may be able to help...but you're not.
[root@CentOS65x64 src]# tar xjf wine-1.9.9.tar.bz2
[root@CentOS65x64 src]# cd wine-1.9.9
[root@CentOS65x64 wine-1.9.9]# ./configure
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for cpp... cpp
checking for ld... ld
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
[root@CentOS65x64 wine-1.9.9]# make
make: *** No targets specified and no makefile found. Stop.
[root@CentOS65x64 wine-1.9.9]# make install
make: *** No rule to make target `install'. Stop.
First of all, why Wine 1.9.9? It's a development release and unless there's some functionality/bugfix in it that you particularly want, you would be best sticking to the latest stable release 1.8.3.
Secondly, why don't you install the EPEL repo version? It would save you a lot of bother.
Hi,
Can anyone please tell me if there is a problem to installation below?
You mean, aside from the VERY OBVIOUS ONE you posted???
Quote:
Code:
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
Is there something in that very clear error that you didn't understand? Since the configure failed, why on earth would you think that running 'make' and 'make install' would somehow work?
AGAIN, as you've been told numerous times now, and spoon-fed instructions on how: LOAD THE EPEL REPOSITORY and TYPE IN 'yum install wine'. That's it. And AGAIN, as you've been asked numerous times now...WHY are you doing this, what is the application, and is there NOT A LINUX EQUIVALENT???? These are simple questions.
You could have installed the EPEL repository and had WINE running in five minutes. And as you've been told numerous times now, this MAY NOT EVEN WORK for your application, do you understand that????
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.