5.20 staging with new .wine runs once, crashes every subsequent time
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
5.20 staging with new .wine runs once, crashes every subsequent time
Never ran into this one before so throwing up here in case it looks familiar to someone. LFS building from source
rm -rf ~/.wine-5.20
WINEPREFIX=~/.wine-5.20 winecfg
It works fine.
If I exit and wait for all processes to end and try to run again I get
002c:fixme:winediag:LdrInitializeThunk wine-staging 5.20 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 0050), starting debugger...
wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 009c), starting debugger...
I didn't notice anything with
WINEDEBUG=+seh
or strace, attaching the logs
rm -rf ~/.wine-5.20
WINEPREFIX=~/.wine-5.20 winecfg
It works fine.
If I exit and wait for all processes to end and try to run again I get
002c:fixme:winediag:LdrInitializeThunk wine-staging 5.20 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 0050), starting debugger...
wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 009c), starting debugger...
I didn't notice anything with
WINEDEBUG=+seh
or strace, attaching the logs
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Did you install or run wine as root?
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Hi! Thank you very much for your reply! I install as root, but run as a regular user.
as reg user:
./configure (x2: 64 bit, 32 bit)
make (x2: 64 bit, 32 bit)
as root:
make install (x2: 64 bit, 32 bit)
as reg user:
rm -rf ~/.wine
winecfg (get the updating .wine popup, winecfg gui comes up)
<exit winecfg, wait till all threads are gone>
winecfg (crashes)
as reg user:
./configure (x2: 64 bit, 32 bit)
make (x2: 64 bit, 32 bit)
as root:
make install (x2: 64 bit, 32 bit)
as reg user:
rm -rf ~/.wine
winecfg (get the updating .wine popup, winecfg gui comes up)
<exit winecfg, wait till all threads are gone>
winecfg (crashes)
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
@invisible kidinvisible kid wrote: ↑Thu Jan 14, 2021 7:19 pm ...
as reg user:as root:Code: Select all
./configure (x2: 64 bit, 32 bit) make (x2: 64 bit, 32 bit)
as reg user:Code: Select all
make install (x2: 64 bit, 32 bit)
)Code: Select all
rm -rf ~/.wine winecfg (get the updating .wine popup, winecfg gui comes up) <exit winecfg, wait till all threads are gone> winecfg (crashes
...
Nothing is leaping out at me, in your attached logs.
Are you able to build vanilla Wine, from source, and run this?
We'd probably need to see the full logs for the actual build, plus the exact commands used.
If you can attach this - it would probably be easier!
Bob
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Thank you very much for the reply! I will do a vanilla build and test and report back with a capture of my process. I can say that this is the same method that I've used for 4.19 and previous, but that might not be useful info for the 5.x series. I will say that any issue that I have that isn't common is probably due to me using the LFS distro and conventions vice a debian-based distro for example.
I am going to try as soon as possible, but might be tied-up tonight and tomorrow. Thanks again, and apologies in advance if it is something I am doing.
I am going to try as soon as possible, but might be tied-up tonight and tomorrow. Thanks again, and apologies in advance if it is something I am doing.
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Interesting! In staging winecfg will come up the first time after removing .wine, but crash afterwords. Vanilla winecfg crashes first time after removing .wine. I've attached all logs. I think if you open 01-commands.txt it will show which logs map to which commands.
- Attachments
-
- wine-5.20-vanilla_capture.tar.xz
- (220.02 KiB) Downloaded 72 times
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
I should also mention I have no "real" /usr/local directory as LFS doesn't require it and leaves it up to you. So my /usr/local -> /usr. You'll see I do use --prefix=/usr. This has only caused me issues like twice out of ~500 packages, but nothing ever serious. For example something I think removed my link and made a real /usr/local directory, but I just manually moved everything and restored the link and the package worked fine. Like twice out of ~500 packages on current install, probably a lot more on previous installs.
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Hi invisible kid,
I've got:
in my Gentoo Portage master make.conf build file.
I noticed that your Wine build has:
in your make logs.
My understanding is that building Wine libraries as non- position independent code can cause problems (as Wine needs to be able force some library mappings in Virtual Memory). Not 100% sure on this though, as I haven't dug into it any depth.
Bob
I've got:
Code: Select all
CFLAGS="... -fpic ..."
I noticed that your Wine build has:
Code: Select all
... -fno-PIC ...
My understanding is that building Wine libraries as non- position independent code can cause problems (as Wine needs to be able force some library mappings in Virtual Memory). Not 100% sure on this though, as I haven't dug into it any depth.
Bob
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Thanks for the reply Bob! That could be it IMO. I'm going to try it first thing in the morning, thx again.
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
I ended up getting 6.0-rc6 vanilla and staging, and noticed they both run fine with a new .wine. Since my goal was to leave 4.x behind and start on a newer release base, I think I'll be okay with 6.x. So I guess I am going to move on. Thanks a lot for your help!
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
@invisible kid
Glad it's working now! You should be able to update to the final Wine stable release of 6.0 now...
I didn't want to complicate matters but Wine is moving towards building most libraries as PE(+) binaries using the mingw64 cross compiler... This was a bit painful to setup on Gentoo - but I think I've got my head around it now!
I guess setting up cross-compilation toolchain, on LFS, might be rather painful though!
I'm not really sure if Alexandre's plan is to ultimately remove support for winegcc built ELF Wine libraries ...
Bob
Glad it's working now! You should be able to update to the final Wine stable release of 6.0 now...
I didn't want to complicate matters but Wine is moving towards building most libraries as PE(+) binaries using the mingw64 cross compiler... This was a bit painful to setup on Gentoo - but I think I've got my head around it now!
I guess setting up cross-compilation toolchain, on LFS, might be rather painful though!
I'm not really sure if Alexandre's plan is to ultimately remove support for winegcc built ELF Wine libraries ...
Bob
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Ahh, okay I will get 6.0 going. mingw64: Yes, this part scares me a little. I tried setting that up a bit ago and mingw64 replaced all my native gcc stuff with mingw64 versions. I had to do a lot of cleanup afterward and was lucky I was able to get myself back to normal, and only because I save all my build directories and was able to go into my original gcc builds and do make installs from there. There were various loose ends to fix when I would try to do something and realized it was broken. It was a nightmare and I'm very scared to go back to that place! I would have to wait for a braver/more competent soul to forge the way and leave instructions.
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
ha, ha fair enough!
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Verified 6.0 staging runs fine. It's unable to run Diablo II or World of Warcraft correctly, so still using 4.19(can run d2), but I know I can build and install 6.x versions of wine if needed in the future. Thanks again for the help.
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Okay, now I realize that nowadays you're not fully compiling wine if you don't have mingw-w64 installed. At least I know I can start from a good place with 6.0-staging. Generally speaking, it seems wine is looking for x86_64-w64-mingw32-gcc and i686-w64-mingw32-gcc. It is also looking for similar versions of clang, but I don't think that's required. mingw-w64 has pretty good instructions once you know what wine is looking for. So it looks like the basic outline will be:
First build binutils by the configuration options: '--prefix=<your-sysroot> --with-sysroot=<your-sysroot> --target=x86_64-w64-mingw32 --enable-targets=x86_64-w64-mingw32,i686-w64-mingw32'
Now we can build first stage of gcc. For configuration of gcc, use configure options: '--target=x86_64-w64-mingw32 --enable-multilib --enable-64bit --prefix=<sys-root> --with-sysroot=<sys-root>'
Now add to your PATH environment the folder <sys-root>/bin. To configure our runtime by the options: '--host=x86_64-w64-mingw32 --enable-lib64 --enable-lib32 --prefix=<sys-root> --with-sysroot=<sys-root>
It looks like I will need to perform the gcc portions twice, once for x86_64-w64-mingw32-gcc, and once for i686-w64-mingw32-gcc.
I did something similar when converting LFS to multilib, and will need to add the mingw-w64 options to the multilib options.
First build binutils by the configuration options: '--prefix=<your-sysroot> --with-sysroot=<your-sysroot> --target=x86_64-w64-mingw32 --enable-targets=x86_64-w64-mingw32,i686-w64-mingw32'
Now we can build first stage of gcc. For configuration of gcc, use configure options: '--target=x86_64-w64-mingw32 --enable-multilib --enable-64bit --prefix=<sys-root> --with-sysroot=<sys-root>'
Now add to your PATH environment the folder <sys-root>/bin. To configure our runtime by the options: '--host=x86_64-w64-mingw32 --enable-lib64 --enable-lib32 --prefix=<sys-root> --with-sysroot=<sys-root>
It looks like I will need to perform the gcc portions twice, once for x86_64-w64-mingw32-gcc, and once for i686-w64-mingw32-gcc.
I did something similar when converting LFS to multilib, and will need to add the mingw-w64 options to the multilib options.
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
@invisible kid
It might be worth taking a look at the Arch Linux mingw package PKGBUILD source files. These are very easy to follow.
E.g. PKGBUILD (mingw-w64-winpthreads 8.0.0-1).
Bob
It might be worth taking a look at the Arch Linux mingw package PKGBUILD source files. These are very easy to follow.
E.g. PKGBUILD (mingw-w64-winpthreads 8.0.0-1).
Bob
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Thanks! This will definitely help. I'll hopefully have a chance to attempt by next weekend.
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
np ... Good luck!
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Okay, so when I started looking at this again I double-checked google, and found I don't have to compile mingw-w64, there are provided binaries. The initial webpage:
https://www.eknori.de/2015-10-23/build- ... -on-linux/
So, I got:
mingw-w32-bin_x86_64-linux_20131227.tar.bz2
mingw-w64-bin_x86_64-linux_20131228.tar.bz2
from:
https://sourceforge.net/projects/mingw-w64/files/
by going to:
Toolchains targetting Win32 -> Automated Builds
Toolchains targetting Win64 -> Automated Builds
I extracted them inside:
/opt/mingw-w32
/opt/mingw-w64
Then when building wine I add them to my PATH:
export PATH=${PATH}:/opt/mingw-w64/bin:/opt/mingw-w32/bin
And wine-staging 6.0 seemed to detect and build with it fine.
Diablo II is working
Wow is working, but without visible mouse pointer/cursor and low framerate
Battle.net comes up but with completely black window
So I'm in a good spot now I think. 4.19-staging will currently run everything but wow, and 6.0-staging can run wow, so I'll just switch between the two until I get everything working with one version. Thanks for all of the help!
Edited to add: Wow cursor started working : D
https://www.eknori.de/2015-10-23/build- ... -on-linux/
So, I got:
mingw-w32-bin_x86_64-linux_20131227.tar.bz2
mingw-w64-bin_x86_64-linux_20131228.tar.bz2
from:
https://sourceforge.net/projects/mingw-w64/files/
by going to:
Toolchains targetting Win32 -> Automated Builds
Toolchains targetting Win64 -> Automated Builds
I extracted them inside:
/opt/mingw-w32
/opt/mingw-w64
Then when building wine I add them to my PATH:
export PATH=${PATH}:/opt/mingw-w64/bin:/opt/mingw-w32/bin
And wine-staging 6.0 seemed to detect and build with it fine.
Diablo II is working
Wow is working, but without visible mouse pointer/cursor and low framerate
Battle.net comes up but with completely black window
So I'm in a good spot now I think. 4.19-staging will currently run everything but wow, and 6.0-staging can run wow, so I'll just switch between the two until I get everything working with one version. Thanks for all of the help!
Edited to add: Wow cursor started working : D
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
Turning off browser hardware acceleration fixes battle.net black window
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
@invisible kid
Ah that's great!
The pre-built mingw-w64 binary tarballs look handy!
Bob
Ah that's great!
The pre-built mingw-w64 binary tarballs look handy!
Bob
-
- Level 5
- Posts: 359
- Joined: Tue Dec 24, 2019 3:23 pm
Re: 5.20 staging with new .wine runs once, crashes every subsequent time
I was pleasantly surprised to say the least!