There is no 64 bit package available.

Bug #43324 reported by Scott Ritchie
60
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned
wine (Ubuntu)
Fix Released
Wishlist
Ubuntu Wine Team

Bug Description

Currently there is no 64-bit Wine package available. The package can in theory be built, however it requires 32-bit libraries in order to run 32-bit windows programs.

This bug depends on 43320 being fixed first.

Revision history for this message
Maxim (maximsch2) wrote :

I can confirm this. I think 64-bit package should be added to edgy eft tree. It should be the same as 32-bit one only with different headers. It should also depend on 32-bit version of libxxf86dga1 or ia32-libxxf86dga1

Maxim (maximsch2)
Changed in wine:
status: Unconfirmed → Confirmed
Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Hi,

I'm trying to build first 64bit packages for native win64 support.
This should be not a difficult task.

For having win32 support on 64bit environments, it needs more then this.
We need to invent new packages, e.g. wine32, which have to be built only on 64bit machines (forgetting ppc architectures first).

I have to talk to Scott Ritchie how we can come to a solution to that.

It would be an improvement, when we would have 64bit support for wine first.

Let's see.

Regards,

\sh

Changed in wine:
assignee: nobody → shermann
importance: Medium → Wishlist
Revision history for this message
stefab (bluefuture) wrote :

I think that there is an already a quite know method for install wine 32 bit on amd 64[1]

Mainly need
libxxf86dga1 (32bit missing)
ia32-libs (already in amd64 repo)
lib32asound2 ia32-libs-sdl (already in amd64 repo)

So i think that is quite trivial to insert a wine32 version in amd64 rerpo.
Any news about this issue?

[1]https://help.ubuntu.com/community/WineForAMD64

Revision history for this message
Scott Ritchie (scottritchie) wrote :

The trick is not forcing the dependencies, it's getting the thing to BUILD on AMD64. All my attempts at that have failed so far.

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Good Morning,

building the last version in edgy (0.9.22) failed for 64bit architectures, because Upstreams 64bit support is somehow broken.

As I said in last reports, I don't like a wine 32bit solution on 64bit architectures...it should compile as native application on 64bit archs....everything else is useless.

Regards,

\sh

Revision history for this message
Maxim (maximsch2) wrote : Re: [Bug 43324] Re: There is no 64 bit package available.

I think you are wrong. 32bit wine is extremely useful on 64bit to run 32bit
windows apps.

On 11/13/06, Stephan Hermann <email address hidden> wrote:
>
> Good Morning,
>
> building the last version in edgy (0.9.22) failed for 64bit
> architectures, because Upstreams 64bit support is somehow broken.
>
> As I said in last reports, I don't like a wine 32bit solution on 64bit
> architectures...it should compile as native application on 64bit
> archs....everything else is useless.
>
> Regards,
>
> \sh
>
> --
> There is no 64 bit package available.
> https://launchpad.net/bugs/43324
>

--

Maxim

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Hi,

on 64bit you could create a 32bit chroot and change into it via dchroot ...
you can install wine 32bit in there and everything is ok.

In my POV it's a better solution then to introduce additional binary packages for only one architecture.

Regards,

\sh

Revision history for this message
Maxim (maximsch2) wrote :

But I think that introducing such binary package is mach better and it seems
to me most users think same.

On 11/16/06, Stephan Hermann <email address hidden> wrote:
>
> Hi,
>
> on 64bit you could create a 32bit chroot and change into it via dchroot
> ...
> you can install wine 32bit in there and everything is ok.
>
> In my POV it's a better solution then to introduce additional binary
> packages for only one architecture.
>
> Regards,
>
> \sh
>
> --
> There is no 64 bit package available.
> https://launchpad.net/bugs/43324
>

--

Maxim

Revision history for this message
Chris Halse Rogers (raof) wrote :

Here's a somewhat ugly debdiff which makes the package successfully build a 32bit wine on x86-64.

It stops the win64 support being built, but I'm not convinced that's a huge loss. As far as I can tell, the overwhelming use-case for wine is win32 programs - there's a huge number of win32 programs with no win64 binary, but I don't know of any win64 program with no win32 binary.

If win64 support is really wanted, I could attempt to make a parallel installable wine32 build, but I'm unsure how successful I'd be.

Revision history for this message
Peter Brown (rendhalver) wrote :

today i was mucking about with building wine from the source packages on my feisty amd64 box as i have been on random occasions for a while.
today i thought i would try getting wine built as a 32bit app.
so using the LDFLAGS from the Ubuntu section of this page http://wiki.winehq.org/WineOn64bit.
i was not sure which file to put them in and after working out that debian/rules seemed to be the place i added those LDFLAGS to this bit of that file.

ifeq ($(DEB_BUILD_ARCH), amd64)
        LDFLAGS="-L/lib32 -L/usr/lib32 -Wl,-rpath,/lib32 -Wl,-rpath,/usr/lib32"
endif

so after much compiling it seems to have worked and i installed the resulting packages and now i am going to do some more testing and see what breaks and what works.

i have generated a diff file and attached it.
my package skills are a little lacking but i am happy to help with more testing as required.

Revision history for this message
Scott Ritchie (scottritchie) wrote :

Peter,

Could you please try running configure with the above flags and --verbose and see if it reports anything missing?

Also, have you made any modifications to the system other than installing packages that are relevant (eg manually linking libraries in /usr/lib32)? Ideally we can incorporate all needed "hand-linking" into the dependencies in a functional 64-bit package.

Revision history for this message
Peter Brown (rendhalver) wrote :

(do you want to see the entire output from the configure?)

OpenGL seems to be missing.
which would explain why directx stuff doesn't seem to work.
---
configure: WARNING: Wine will be build without OpenGL or Direct3D support
configure: WARNING: because something is wrong with the OpenGL setup:
configure: WARNING: No OpenGL library found on this system.

---

i don't think i have made any symlinks in the /usr/lib32 directory but i could be wrong.
like i said i have been mucking around with this for a while so i may have made symlinks a while ago while i was trying to build wine from source instead of a package.

i can uninstall all my lib32 and ia32 packages and check and then reinstall them if you like.

Revision history for this message
Chris Halse Rogers (raof) wrote :

I'm pretty sure you need to hand-link at least some of the GL libraries (which my debdiff does - it built correctly in a pristine pbuilder). I might see how much of it is still necessary with 0.9.29, though.

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

hi Scott,

if you want to add wine 32bit packages to 64bit archs, please add new binary packages to it, like (lib)wine32, which are only build on 64bit archs like amd64 or emt64.

Don't use libwine/wine package names, because they should be reserved for arch dependent packages.

so (lib)wine on i386 are 32bit packages and on amd64 they are 64bit packages.
(lib)wine32 on amd64/emt64 are 32bit packages for x86_64bit archs.

Regards,

\sh

Revision history for this message
David Farning (dfarning) wrote :

This appears to be a wine related thread. Please open a seperate firefox issues if necessary.

Thanks
David

Changed in firefox:
status: Unconfirmed → Rejected
Revision history for this message
Scott Ritchie (scottritchie) wrote :

Having recently obtained access to a 64 bit virtual machine, I was able to attempt making a proper 64 bit package today.

I combined elements of Chris Halse Rogers hack with an email I got from Ken Geis. I'll be uploading the 64 bit packages for Feisty to the winehq APT repository sometime tomorrow for proper testing. Hopefully they'll soon be able to make their way into backports.

As for \sh's concerns about Wine being built as a 32 bit application, don't fret: the upstream plan is for Wine to ALWAYS support 32 bit applications. Once win64 is working properly, Wine will be built with both 64 bit and 32 bit library support. For this reason there's no need for a separate 32 bit Wine package, as such a package will ultimately just be a subset of the 64 bit one (when it actually can be made to work upstream).

Thank you everyone,
Scott Ritchie

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Hi Scott,

my concerns were not "to not support win32 anymore" but, to have different packages for wine32 on 32 and 64bit.
There will be support for 32bit and 64bit wine, but to have 32bit support on 64bit archs we have to provide separate packages for wine32 on 64bit archs (e.g. wine for 32bit archs and native 64bit and wine32 for 32bit wine on 64bit archs).

If we can get this into gutsy, I would be happy :)

\sh

Revision history for this message
emk (eric-kidd) wrote :

Thanks, Scott Ritchie!

I've tested the packages in the repository described at http://www.winehq.org/site/download-deb on a clean 64-bit Feisty system, and everything seems to work fine.

As you can see, I didn't have any 32-bit packages on my system before the install:

$ sudo apt-get install wine msttcorefonts libasound2-plugins
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  cabextract ia32-libs lib32asound2 lib32gcc1 lib32stdc++6 lib32z1 libc6-i386
  libpulse0 libsamplerate0
Suggested packages:
  pulseaudio
The following NEW packages will be installed:
  cabextract ia32-libs lib32asound2 lib32gcc1 lib32stdc++6 lib32z1
  libasound2-plugins libc6-i386 libpulse0 libsamplerate0 msttcorefonts wine
0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.4MB of archives.
After unpacking 107MB of additional disk space will be used.
Do you want to continue [Y/n]?

I've installed and run an in-house Win32 application without any trouble. Slick! It would be great to get this patch into Gutsy.

Changed in wine:
assignee: shermann → ubuntu-wine
Revision history for this message
Adam Petaccia (mighmos) wrote :

Should we begin to transition package names for i386 archs as well? I think that might make life a little more easier than the overall picture we currently have now. I.E: i386 can install wine32 (wine becomes a transition package for a release), while AMD64 users have their choice of wine64 or wine32. Also, I can't find the resource, but I seem to recall there being issues with what if a 64-bit application expects to call a 32 bit one. This would require both wine64 and wine32, which I don't believe are parallel installable at the moment. Also, see http://winehq.org/?issue=318 for a few more issues with `wine64'.

So long story short, we may want to transition to calling our package "wine32" on all archs, even though "wine64" probably won't come around for a while (yes, even though it does compile).

Revision history for this message
Loye Young (loyeyoung) wrote :

Just to throw in some perspective, . . .

Windows Vista has had problems with software compatibility on 64-bit machines. Even fans of Windows (the poor souls) have complained about it. See http://forums.jinx.com/topic.asp?TOPIC_ID=60206 and http://extended64.com/blogs/rhoffman/archive/2006/12/23/One-Month-Later_3A00_-My-experiences-with-Windows-Vista.aspx.

My sense is that the team (both (*)Ubuntu and upstream) have been doing a great job making progress on this front. That doesn't mean we should let up (wouldn't it be cool if wine64 ran better than Win64?), but it does suggest that there is cause for optimism.

Loye Young

Revision history for this message
Alex F (frase) wrote :

I just installed Feisty on an AMD64 (X2 6000+ to be exact), and I still have not been able to get wine to run. Everything I've tried results in 'segmentation fault' on winecfg, apparently as it tries to create the ~/.wine path and establish a faux-registry.

I tried emk's instructions a few posts up (2007-05-14, referencing http://www.winehq.org/site/download-deb) with the same result. I've also tried compiling from source (wine 0.9.39) according to a few other tutorials, including CFLAGS=-fno-stack-protector and CC=gcc-3.4, CXX=g++.3.4, also to no avail.

Next I guess I'll try compiling 0.9.37 from source with various combinations of those flags, since that seems to be the version that was 'released' as a package for Feisty, but I'm running out of ideas.

Help?

Thanks,
Alex

Revision history for this message
Andres Mejia (amejia1) wrote :

amd64 packages exist for wine in Debian but only up to version 0.9.34.

http://ftp.debian.org/debian/pool/main/w/wine/
dget http://ftp.debian.org/debian/pool/main/w/wine/wine_0.9.34-1.dsc

We should take a look to see what is done to create the amd64 packages.

Revision history for this message
Loye Young (loyeyoung) wrote :

On Wednesday, June 27, 2007 12:20:46 am Andres Mejia wrote:
> amd64 packages exist for wine in Debian but only up to version 0.9.34.
>
> http://ftp.debian.org/debian/pool/main/w/wine/
> dget http://ftp.debian.org/debian/pool/main/w/wine/wine_0.9.34-1.dsc
>
> We should take a look to see what is done to create the amd64 packages.

Apparently the problem is that Windows is a 32bit OS, so amd64 > 32 bit >
Windows includes an additional layer of issues that x86 doesn't have.

Scott Ritchie was working on that upstream. Last September, he ran into some
problems getting wine to compile on amd64. See
http://www.winehq.org/pipermail/wine-devel/2006-September/051015.html. I
think he made some progress since then, but I don't know the latest. His
email address may be found on the winehq.org mailing list (google: wine amd64
scott-ritchie).

Loye Young

Revision history for this message
Scott Ritchie (scottritchie) wrote :

The 64 bit version compiles fine now, and I'll be moving it into Gutsy universe soon. You can get it already for Feisty here: http://winehq.org/site/download-deb

Revision history for this message
Kalrog (nathan-deckinga) wrote :

I'm glad I checked before logging a new bug. This still seems to be an issue for Gutsy (i.e. it hasn't been moved into the Gutsy universe yet).

Revision history for this message
Scott Ritchie (scottritchie) wrote :

Actually, I'm not an MOTU so someone else needs to upload it to Gutsy for me.

packages.ubuntu.com says the Wine in Gutsy is 0.9.42, which I'm assuming is the package I made. But it's not being built in 64 bit mode. Could whomever is responsible for merging in the package contact me?

Revision history for this message
Pär Lindfors (paran) wrote :

Does this package contain a 64-bit wine binary? Will that binary run 32bit Windows applications? If not then I think it would be a big misstake to include it.

The thing users want when they install wine is to run some specific Windows program, and probably 99.9% of all Windows programs is only distributed as 32bit binaries.

Revision history for this message
Kalrog (nathan-deckinga) wrote :

I agree that I want to be able to run 32bit windows binaries, but I can't do that right now because there is NO wine package available to me in Gutsy (at least as far as I can tell). Specifically, I am running an AMD x2 so I picked the 64bit KUbuntu to go with that. If I have just missed the available wine package, then that is great and I will be done - but I have looked and didn't find one.

Revision history for this message
Scott Ritchie (scottritchie) wrote :

The "64 bit package" I put at winehq is actually a 32 bit version (that only runs win32 and win16 apps), built to link against the 32 bit libraries on the 64 bit version of Ubuntu (which are in a different place than in the 32 bit version).

So, yes, it's what you want, and I'm not sure why it's not being built in Gutsy.

Revision history for this message
Scott Ritchie (scottritchie) wrote :

Actually, it is being built in Gutsy, but the build script is failing: http://launchpadlibrarian.net/8598218/buildlog_ubuntu-gutsy-amd64.wine_0.9.42-0ubuntu1_FAILEDTOBUILD.txt.gz

I'll have to install Gutsy and take a look at it myself.

Revision history for this message
Kalrog (nathan-deckinga) wrote :

Scott - It seems like I already have the platform around to take a look. How can I help?

Revision history for this message
Andres Mejia (amejia1) wrote :

It looks like building 32-bit wine on amd64 will be possible soon, if it's not possible now. Take a look at http://buildd.debian.org/pkg.cgi?pkg=wine
Also, these links should be relevant.
http://bugs.debian.org/430845
http://bugs.debian.org/394230
http://bugs.debian.org/381341

A sync request should probably be placed for when wine-0.9.42 packages get uploaded to the Debian archive. Just one more version according to http://packages.qa.debian.org/w/wine.html

Revision history for this message
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote :

So, will this be in Gutsy or not?

Revision history for this message
Andres Mejia (amejia1) wrote :

I filed a sync request for wine-0.9.42-1 from Debian. (bug #137566)

Hopefully these packages do get merged in time for the release of Gutsy.

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

It appears that a 64 bit build for wine has been in Debian since 0.9.29-1 (21st of January). This is the problem when people don't merge Debian changes.

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Ladies & Gentlemen,

Debian is for wine not our upstream.
Furthermore, the debian package is evil and ugly.

We are working on an approach which is far better, and follows the Ubuntu way (compiling everything from source).

Kind Regards,

\sh

Revision history for this message
Andres Mejia (amejia1) wrote :

Even better, there's wine-0.9.44 packages being worked on. http://revu.tauware.de/details.py?upid=184

Revision history for this message
jojoaditya (jojoaditya) wrote :

well than... it seems there is a new bugs again.... if u running beryl or compiz fusion, just try to press alt+f4 at the desktop... and it will turned into text mode... tty2.. just try that bugs... please check... and reply. u must run on ubuntu. thx

---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.

Revision history for this message
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote :

@jojoaditya

That's not a bug. You have 6 text-consoles available (control+alt+f1 upto control+alt+f6)
Control+alt+f7 will bring you back to the graphical desktop.

Although the common user wouldn't need or use this, the more experienced users can use this to reset GDM for example. Also this is completely unrelated to _this_ bug-post about wine. You might not have noticed that when you reply to these emails you have been receiving, your reply becomes a comment on the specific bug-page on launchpad. So, if you want to report others bugs, not related to this bug, please go to http://launchpad.com/ubuntu and click on the report a new bug button.

Please use the email-reply only for comments relating to the specific bug discussed there.
Thank you.

Revision history for this message
Pär Lindfors (paran) wrote :

wine 0.9.45 for amd64 is in gutsy now.

Changed in wine:
status: Confirmed → Fix Committed
Changed in wine:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.