https://bugs.winehq.org/show_bug.cgi?id=40034 --- Comment #25 from Austin English <austinenglish(a)gmail.com> --- (In reply to alyssianagrace from comment #23)
(In reply to Austin English from comment #22)
You can run wine from the build directory. E.g., instead of doing: $ wine foo.exe
do: $ ~/path/to/1.9.2/wine foo.exe
Then let us know what happens.
[alyssa(a)parrot]─[~] └──╼ $~/path/to/1.9.2/wine foo.exe
you need to adjust the path to where your wine build is (looks like ~/wine-git/wine) / exe name (setup.exe). (In reply to alyssianagrace from comment #24)
(In reply to alyssianagrace from comment #23)
(In reply to Austin English from comment #22)
You can run wine from the build directory. E.g., instead of doing: $ wine foo.exe
do: $ ~/path/to/1.9.2/wine foo.exe
Then let us know what happens.
[alyssa(a)parrot]─[~] └──╼ $~/path/to/1.9.2/wine foo.exe bash: /home/alyssa/path/to/1.9.2/wine: No such file or directory This is what popped up
I also ran this: [alyssa(a)parrot]─[~/wine-git] └──╼ $sudo make install [sudo] password for alyssa: make: *** No rule to make target 'install'. Stop.
It looks like you didn't actually build wine just downloaded the source (and maybe applied the patch?). You need to run ./configure && make. If you need help with the above, please use the forums or #winehq on Freenode -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.