SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Actually wine is available as a 64bit application but there seems to be no such thing as a pure 64 bit windows app (or at least the installers aren't) so it's pretty useless.
I was hoping to not make a new thread, so I'll post in this one. In Slackware 64bit I cannot get Wine to (seemingly) install or run correctly.
I tried, in this order:
Installing Wine 64Bit directly;
Using AlienBob's multilib (the tons of tiny files to download was a huge pain, but it did go through without any errors in the end)
Installing Wine afterwards via the SlackBuild
Now, the wine install attempt from SlackBuild had A LOT to do, I mean it was taking 15-20 min, and in the end it came up with some WineGCC error and stopped.
If you tell me what to do in order to get you correct diagnostic output I'll happily and quickly do so, but I have no idea how to do diagnostics on it myself, let alone remove for a clean try.
I was hoping to not make a new thread, so I'll post in this one. In Slackware 64bit I cannot get Wine to (seemingly) install or run correctly.
I tried, in this order:
Installing Wine 64Bit directly;
Using AlienBob's multilib (the tons of tiny files to download was a huge pain, but it did go through without any errors in the end)
Installing Wine afterwards via the SlackBuild
Now, the wine install attempt from SlackBuild had A LOT to do, I mean it was taking 15-20 min, and in the end it came up with some WineGCC error and stopped.
If you tell me what to do in order to get you correct diagnostic output I'll happily and quickly do so, but I have no idea how to do diagnostics on it myself, let alone remove for a clean try.
Did you follow this section on AlienBob's Site?
Quote:
Compiling 32-bit programs
In case you need to compile a 32-bit program (wine and grub are two examples of open source programs that are 32-bit only) you first configure your shell environment by running the command:
. /etc/profile.d/32dev.sh <--- THIS RIGHT HERE
Note the 'dot' in front of the filename - that is actually part of the commandline! Running this command changes or creates several environment variables. The effect of this is, that 32-bit versions of binaries are preferred over 64bit binaries when you compile source code - you will be running a 32bit compilation. The effect will last until you logout from your shell.
In this changed environment, you will be able to use standard SlackBuilds to build 32-bit packages for Slackware64. There are two things to keep in mind:
You will have to define the ARCH variable as 'x86_64' even though you are compiling a 32-bit program!
This is related to the triplet of “$ARCH-slackware-linux” which is normally used in the “configure” command. Also, try setting the ARCH to for instance “i486” and you will see that the CFLAGS definition for that architecture will result in gcc errors like ”compiler can not create executables”. This is related to the design of a SlackBuild script. Rather than editing the script and change/remove CFLAGS definitions, you can set the ARCH to “x86_64” and save yourself some time. The real work is being done by the 32dev.sh script.
You will have to edit the SlackBuild if it wants to use 'lib64/' directories for “$ARCH = x86_64”. You have to force it to use 'lib/' directories instead. Usually, this is accomplished by finding a definition like:
Hi there! I see you've bumped my thread and since I made it Wine has been working well for me.
Well, just to start off did you install wine's dependencies?
Quote:
This requires fontforge and webcore-fonts.
I believe both can be found from SlackBuilds.org. Other than that, another solution is to use a pre-built package from wine's official website: http://www.winehq.org
This doesn't mean you won't be needing Alien Bob's multilib packages.
Here you can download both the stable and development version.
I sure didn't. To be honest, it's kinda above my head right now. I'm an experienced programmer (so configuring the config files for stuff and building things is quite familiar) but not a regular Linux user, so please forgive me. Can I get you (or another kind soul) to give me some context or explain how to implement (other than running the first line from terminal).
Quote:
Originally Posted by Konphine
Hi there! I see you've bumped my thread and since I made it Wine has been working well for me.
I did, I figured it was a good place to start for answers! I read quite a few posts before posting, and was hoping to avoid creating a new thread.
I did NOT do that either, boy every minute I feel a little dumber, hah! I'm going to get to googling on those dependencies, I'll update as soon as they are installed.
UPDATE:
Alright, what I've done is created the above 32dev file if I understand it correctly, by running the statement in my terminal.
I also installed the dependencies as outlined by Konphine.
That causes this now when I try to run a win32 program.
Quote:
Originally Posted by CODE
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
fixme:actctxarse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
wine: Unhandled stack overflow at address 0x7ef7c8ba (thread 0009), starting debugger...
err:seh:setup_exception_record stack overflow 1284 bytes in thread 0009 eip 7ef95f23 esp 07650e2c stack 0x7650000-0x7651000-0x7850000
UPDATEx2:
After getting some food in my stomach, and things got quieter in the house, I re-read bassplayer69's post, and it seems incredibly straightforward.
I'm following the instructions on there right now (I hope correctly) and we'll see if it builds correctly. In the meantime, does anyone know when it finishes what's a reliable way to test for success? (Even though my stuff is broken/incorrect, I can still open some things, like a very old simcity2k urban editor (very random executable attempt)).
UPDATEx3:
After a VERY long wait on the SlackBuild as mentioned above, it make an installer, which installed successfully.
When I try to run a test program afterward, it gives me this:
Quote:
sh-4.1$ wine eduke32.exe
preloader: Warning: failed to reserve range 00010000-00110000
wine: '/home/Chris/.wine' is a 64-bit installation, it cannot be used with a 32-bit wineserver.
UPDATEx4:
Deleted the .wine folder, let it create a new one. COULD NOT start a few applications, it would spit out same memory address errors at me, but for some reason, it loaded up Diablo 2 as if it was native. Bizarre.
Any advice guys?
Last edited by TheParoxysm; 10-08-2011 at 03:53 AM.
Reason: Update4
With no issues, ran as smoothly as on windows and with no fidgeting needed.
Quote:
Originally Posted by AlienBob
This is an error that you can resolve.
I actually discovered that last night, right before hitting the sack. I even made the conf file needed since it didn't exist on my system so I wouldn't need to continually do so.
I think once I confirm that I have a proper setup, I'll set up a VM with a fresh slack64 install and test a streamlined install. If I can get it simple and understand it well it might not be a bad idea to write a little guide on it.
Luckily I don't need much from Win, so it's not a big deal if I can't get 100% compatibility.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.