[SOLVED] Help compiling a patch for wine

[davidbrooke]

I'm looking to test a patch from the wine-staging group but it needs to be compiled. I'm not sure how to approached this, since I've never compiled anything.
Here is the link for the patch:
https://bugs.wine-staging.com/show_bug.cgi?id=528#c13

If someone could help me, possibly step by step till completion, it would be appreciated.
Thanks

[Roman_Gruber]

usually you do something like

git clone git repository url

to get hte stuff from git

than apply the patch somehow

than run gcc, it depends on every software

sometimes its just make

other things need to use make + makeconfigfileblablaprovided by the software

so it is a bit different every time.

No idea if wine uses git at all.
Any tutorial for building from source is quite reasonable in this context, google is your friend for example.

and also a warning, git software tends to not compile at all, when you can not read code, or try to understand it to fix it, you are quite running in a dead road...
i tried building eternal lands, some space games from source, naev, ... some build decently others quite fail because of outdated libaries, weird code, wrong coding style, wrong declaration of libaries or c statements, ...
and also the gcc in use makes things also worse...
newer gcc complain more than older version sometimes ...

I am sure there is somewhere a tutorial => how to compile wine from source in linux. look that up, and do it...

[Chiitoo]

davidbrooke,

Is it that you only want to test one patch, or is simply enabling the staging USE-flag not an option for some other reason(s)?

Looking at the bug, I guess it's a very new patch so it's not in it yet. If that is indeed the case, I think you could simply toss the patch under

/etc/portage/patches/app-emulation/wine

and be done with it. ^^

If the patch fails to apply on 1.7.50, using git would probably be the most easy way out. I'm sure DuckDuckGo et al. can find a plethora of guides, but I'd probably suggest on checking the official ones, like this for example: http://wiki.winehq.org/FAQ#compile_wine

[davidbrooke]

davidbrooke,

Is it that you only want to test one patch, or is simply enabling the staging USE-flag not an option for some other reason(s)?

Looking at the bug, I guess it's a very new patch so it's not in it yet. If that is indeed the case, I think you could simply toss the patch under

/etc/portage/patches/app-emulation/wine

and be done with it. ^^

Yes I want to test the patch. I don't understand "simply toss the patch under /etc/portage/patches/app-emulation/wine". What exactly is involved?
Thanks

[asturm]

Patches under that directory (also possible including version atom) will be automatically applied during src_prepare if the ebuild has implemented epatch_user, without any further interaction required by you. Just look for the patch really being applied at the beginning of emerge.

[davidbrooke]

So here is the process that I understand so far....
1. Create a text file: (using https://github.com/wine-compholio/wine- ... BIOS.patch)
/etc/portage/patches/app-emulation/wine/0001-wbemprox-Set-bios-name-in-Win32_BIOS.patch
2. Copy the following into /etc/portage/patches/app-emulation/wine/0001-wbemprox-Set-bios-name-in-Win32_BIOS.patch:

Code: Select all

From d72d7f4a70a9715458b4cbd60c5a951e74770448 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michael=20M=C3=BCller?= <michael@fds-team.de>
Date: Thu, 27 Aug 2015 01:55:42 +0200
Subject: wbemprox: Set bios name in Win32_BIOS.

---
 dlls/wbemprox/builtin.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/dlls/wbemprox/builtin.c b/dlls/wbemprox/builtin.c
index 1c960eb..8f51453 100644
--- a/dlls/wbemprox/builtin.c
+++ b/dlls/wbemprox/builtin.c
@@ -377,7 +377,8 @@ static const struct column col_bios[] =
     { prop_releasedateW,        CIM_DATETIME },
     { prop_serialnumberW,       CIM_STRING },
     { prop_smbiosbiosversionW,  CIM_STRING },
-    { prop_versionW,            CIM_STRING|COL_FLAG_KEY }
+    { prop_versionW,            CIM_STRING|COL_FLAG_KEY },
+    { prop_nameW,               CIM_STRING }
 };
 static const struct column col_cdromdrive[] =
 {
@@ -666,6 +667,8 @@ static const WCHAR bios_smbiosbiosversionW[] =
     {'W','i','n','e',0};
 static const WCHAR bios_versionW[] =
     {'W','I','N','E',' ',' ',' ','-',' ','1',0};
+static const WCHAR bios_nameW[] =
+    {'W','I','N','E',' ','B','I','O','S',0};
 static const WCHAR cdromdrive_mediatypeW[] =
     {'C','D','-','R','O','M',0};
 static const WCHAR cdromdrive_nameW[] =
@@ -765,6 +768,7 @@ struct record_bios
     const WCHAR *serialnumber;
     const WCHAR *smbiosbiosversion;
     const WCHAR *version;
+    const WCHAR *name;
 };
 struct record_cdromdrive
 {
@@ -1041,7 +1045,7 @@ static const struct record_baseboard data_baseboard[] =
 static const struct record_bios data_bios[] =
 {
     { bios_descriptionW, bios_descriptionW, bios_manufacturerW, bios_releasedateW, bios_serialnumberW,
-      bios_smbiosbiosversionW, bios_versionW }
+      bios_smbiosbiosversionW, bios_versionW, bios_nameW }
 };
 static const struct record_computersystemproduct data_compsysproduct[] =
 {
-- 
2.5.0

3. Re-install wine
sudo emerge -av wine
4. Test

[davidbrooke]

It appears that the patch was applied, terminal output during wine re-install:

Code: Select all

* Applying user patches from /etc/portage/patches//app-emulation/wine ...
 *   0001-wbemprox-Set-bios-name-in-Win32_BIOS.patch ...      

I tested the app and the problem was resolved.
Thanks everyone for your help!