[Bug 48533] New: Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

Bug ID: 48533
           Summary: Cannot run source Wine at all
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wineserver
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Every way I try to build and run Wine is blocked. I'm at a loss of how to get
it working on Fedora 31.

Run without distro Wine installed, it fails because it needs runtime
dependencies which I can't find. Nothing seems to list dependencies for that.

Run with distro Wine installed it fails with wineserver version error. Change
version and it fails with kernel error. Search and eliminate any other
wineserver and it still fails. Reboot, whatever nothing works.

Tried master and stable branches. Still no go.

The building Wine source guide and/or Wine completely fail here.

Is there some way past this or do I need a different distro like Ubuntu? Maybe
GDB can list the dependencies which I haven't tried?

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
          Component|wineserver                  |-unknown

--- Comment #1 from Zebediah Figura  ---
(In reply to ryan from comment #0)
> Every way I try to build and run Wine is blocked. I'm at a loss of how to
> get it working on Fedora 31.
>
> Run without distro Wine installed, it fails because it needs runtime
> dependencies which I can't find. Nothing seems to list dependencies for that.

Does it fail to build, or fail to run? Note that you don't need everything that
configure checks for.
> Run with distro Wine installed it fails with wineserver version error.
> Change version and it fails with kernel error. Search and eliminate any
> other wineserver and it still fails. Reboot, whatever nothing works.

One possible cause of this is reusing the same build tree for multiple
architecture builds. I would first try "rm -r wine wine64 loader" in your build
tree(s), and rebuilding, and see if that helps.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #2 from [e-mail] ---
> Does it fail to build, or fail to run? Note that you don't need everything that
> configure checks for.

Building is fine. Just running it where the problem is. This is besides being
unable to build 32 bit - ran into too many problems with LXC, don't need 32 bit
prefix anyway, and as far as I can tell it shouldn't stop building using
configure --enable-win64 and from not running a 64 bit prefix.
> One possible cause of this is reusing the same build tree for multiple
> architecture builds. I would first try "rm -r wine wine64 loader" in your build
> tree(s), and rebuilding, and see if that helps.

Using make and its refusing to build with stuff missing as a result of that. Am
assuming that you're not talking about something highly specific that doesn't
affect make negatively but I've tried it various ways and no matter what I do
make and configure just doesn't like that.

I think the next highest probability of working is if I use Ubuntu so that will
probably be next. Thank you for trying. Will update if it works.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #3 from Zebediah Figura  ---
(In reply to ryan from comment #2)
> > Does it fail to build, or fail to run? Note that you don't need everything that
> > configure checks for.
>
> Building is fine. Just running it where the problem is. This is besides
> being unable to build 32 bit - ran into too many problems with LXC, don't
> need 32 bit prefix anyway, and as far as I can tell it shouldn't stop
> building using configure --enable-win64 and from not running a 64 bit prefix.

Can you please attach console output as well as config.log?
> > One possible cause of this is reusing the same build tree for multiple
> > architecture builds. I would first try "rm -r wine wine64 loader" in your build
> > tree(s), and rebuilding, and see if that helps.
>
> Using make and its refusing to build with stuff missing as a result of that.
> Am assuming that you're not talking about something highly specific that
> doesn't affect make negatively but I've tried it various ways and no matter
> what I do make and configure just doesn't like that.

Whoops, that was my mistake, I forgot that'll get rid of loader/Makefile. I
think rerunning configure first should resolve that.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #4 from Austin English  ---
(In reply to ryan from comment #2)
> > Does it fail to build, or fail to run? Note that you don't need everything that
> > configure checks for.
>
> Building is fine. Just running it where the problem is. This is besides
> being unable to build 32 bit - ran into too many problems with LXC, don't
> need 32 bit prefix anyway, and as far as I can tell it shouldn't stop
> building using configure --enable-win64 and from not running a 64 bit prefix.

While you can build a 64-bit only wine, note that many 64-bit applications mix
in  32-bit components and that will fail with such a setup.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #5 from [e-mail] ---
> While you can build a 64-bit only wine, note that many 64-bit applications mix
> in  32-bit components and that will fail with such a setup.

Its possible I could miss something silly but the application installer works
using the distro wine and 64 bit prefix and the application does as well.

Source wine failure:
$ ,/wine <exe-to-install>
wine client error:0: version mismatch 595/596.
Your wineserver binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?

git master version looks to be supplied by #define SERVER_PROTOCOL_VERSION 595
as is currently at 595. I'm confused where 596 is coming from though. It
shouldn't be distro if master is at 595.

Changing SERVER_PROTOCOL_VERSION to 596 result in a different error. -k of
wineserver and using source wineserver does nothing. Removing all wineservers
but source does nothing.

$ sudo dnf remove --allowerasing wine
$ ,/wine <exe-to-install> also has failure (of course from lack of runtime
dependencies):
...<exe-to-install>" not supported on this system
Also does this regardless of supply of prefix eg "WINEPREFIX="..." ./wine"

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #6 from minion  ---
i build wine from fedora 31 without any issues.

I found it pretty easy to setup:

dnf install "Development Tools"
dnf build-dep wine-devel

and then try ./configure --enable-win64 && make -jN

this is pretty much all you need. youll be missing a couple packages that are
optional. now you can run from your build tree.

./wine --version should print your running git version.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

minion  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #7 from minion  ---
not knowing what you did to your build tree at this point, i typically build
wine using a shell script and i run this at the top which always resets me to
latest git gracefully.

make distclean
rm -rf wine64-build
rm -rf wine32-build

git add .
git reset --hard HEAD
git pull

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #8 from [e-mail] ---
Does 64 bit prefix make use of 32 bit wine code at all?

Thanks a lot to all :-D

I looked deeper into 64 bit exe and my own application exe which is 64 bit runs
using wine source here (and even does so without distro wine installed).

Not sure why the application I want to run will install to 64 bit prefix though
but not with custom wine 64 bit.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #9 from minion  ---
it's probably better to try in a separate prefix for your custom build

WINEPREFIX=/path/to/prefix ./wine theprogram

i also believe 64 bit winebuild is wow64 enabled.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #10 from [e-mail] ---
> While you can build a 64-bit only wine, note that many 64-bit applications mix > in  32-bit components and that will fail with such a setup.

Currently wondering if that answers my previous question that a 64 bit prefix
may make use of 32 bit wine code. It sounds like this might what is meant.
> make distclean
> rm -rf wine64-build
> rm -rf wine32-build
>
> git add .
> git reset --hard HEAD
> git pull

Same problem. It starts but then fails as above.
> WINEPREFIX=/path/to/prefix ./wine theprogram

Yes, did that mostly for a while to not conflict with distro installed wine.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #11 from Zebediah Figura  ---
Wine itself can run successfully in a 64-bit-only prefix, but many "64-bit"
applications include 32-bit components, including installers.

If your application works in a 64-bit environment, then there is probably not
much reason to try to build 32-bit Wine.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

--- Comment #12 from [e-mail] ---
> If your application works in a 64-bit environment, then there is probably not
> much reason to try to build 32-bit Wine.

Could be that I'm thinking it was but it wasn't. But of course, I did try it
with a 32bit only prefix and it wouldn't install so took that to mean 32 bit
wouldn't be needed. Missed the Wow64 part of the wine guide because of that.
Crazy me.

Might as well exhaust the possibility at this point before trying Ubuntu as I
have to partition and install that to an old laptop which will take forever to
build wine.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #13 from [e-mail] ---
Considering this solved.

WoW64 Wine on Ubuntu does allow the application to work from source build. I
haven't tested non-Wow64 Wine on Ubuntu with the application and have no reason
to at this point.

With Fedora, I ran into both LXC 2.0 and 3.0 having problems with the
containers that looked like they would require too much time to work through.
After seeing that, just went and installed Ubuntu.

Thank you to everyone.

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
             Status|RESOLVED                    |CLOSED

--- Comment #14 from André H.  ---
closing invalid

[Bug 48533] Cannot run source Wine at all

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48533

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
            Version|unspecified                 |5.0