Of cause i could download and compile/fatch libxml2 and libxstl in users directory. But just exchange the final compiled files libexslt.so.0.8.17 libxml2.so.2.8.0 libxslt.so.1.1.28 is not enough. I also download the libxml2-devel Packages. Seems that i made something wrong or missed some pyhton-related packages.

So my configure Step of wine still say the versions are to old or did not fit each other. Thought this is the quick and dirty way because

Stefan Dösinger wrote:

I've solved that Gentoo problem by compiling an up-to-date libxml2 by hand and
installing it to /usr/lib32. That is a better solution IMO.

Now I'll try to modify these ebuilds and create a local overlay for libxml2-devel, libxml2 and libxslt. And here is my main-question. Gentoo have no libxml2-devel Package?

Ok, since Gentoo will compile all the stuff and other Linux distributions don't i suppose that the libxml2 and libxslt ebuilds handle the libxml2-devel part. But i can not rewrite the actual ebuilds myself to use the up to date git repository of these packages.

Seems that i have to wait till wine 1.7.1 is in portage.

Edit: Thank you very much Alexandre Rostovtsev and Austin English, I am patient.

Thank you very much haarp! Apparently i missed that clear solution at the thought of an update on libxml2.

Never thought that an update in Gentoo of these two packages will be so intractable. But hey if the libxml2 and libxml2-devel Project Pages which got rarely new packages and have 32bit and 64bit Versions. Just for parsing and creating xml files! I underestimate the complexity/dependency.

I started with the thought "copy an X.dll or Xlib-File into /usr/lib32/" to fix this. Patching wine before compilation is great :D

I've been using the FireBurn Overlay. Has a newer build of libxml2 (possibly with just that offending commit removed)... Anyway using this Overlay works fine for me - when building Wine >=1.7.1... The guy maintaining the Overlay seems to be quite helpful as well...

New ebuilds are avaiable for wine -1.7.3 and -9999, but with a lot of blockers if you are mainly compile with stable partage branch._________________Mircosoft software is like having sex with a stranger, you always have to be careful not to get infected with something...

The suggested wine3d-Patches by Stefan Dösinger working nice, still just a little unstable. Since i am not sure if his Patches work with wine 1.7.4 too i just use two different Versions of wine, that one in Portage and for testing the manual updated, patched and compiled Version in my Users directory. Since the official wine branch got more updates then these pages topically ill i did not need an overlay.

I have not managed to compile the latest wine, because of the already mentioned blockers, can someone post me the packages.keywords /packages.use, that is enabling me to successfully compile latest wine in testing branch ?

Sorry for asking and thank you ;O)_________________Mircosoft software is like having sex with a stranger, you always have to be careful not to get infected with something...

Haarp, I have downloaded your git repo zip file and then I execute the script you provided for AMD64 users, but I get this when I compile :

make: *** No rule to make target `dlls/ntoskrnl.exe/ntoskrnl.exe.spec', needed by `dlls/ntoskrnl.exe/libntoskrnl.exe.def'. Stop.

I have installed the libs that you commented are needed to complie, but I am probably missing something !

Thanks

You certainly are missing something there!

Specifically, dlls/ntoskrnl.exe/, which is nowhere to be found on the sources mentioned above. I can't think of a reason for the why, perhaps I'm just doing it wrong, but I see some other things there that I suspect will lead into a failed build even if one were to get the missing files from another source.

Whether or not you're interested, here's exactly what I meant by using git in my earlier posts.

Just some sleepy thoughts (sorry for any possible mistakes, lurking).
I hope they be helpful for someone, somehow.

Oh and if the libxml2 issue is still an issue (I think the fix is only in 'unstable' at the time of writing), either use the patch available in the sources that has been mentioned by others, or use the one below, which I created some time ago for people at Wine AppDB.

Simply paste the contents of this (http://bpaste.net/show/130852/) into a file, then (at the top-level of the Wine git clone's path) use the patch command:

Code:

patch -p1 < what-ever-you-named-the-file.patch

Edit:

I should add that all this wont install Wine (I generally keep Wine installed via Portage, so I suggest running Wine from source in this case). That is, you would need to include the path to the Wine you built from git to use it.

Ok ! I made it to compile it on 64bit compat mode ... but now I don't have regedit or winecfg .... where are the tools bins supossed to be ? Oh and ... creating wine prefix doesn't work as usual, should I do it from the source too ? It doesn't seems to work ...

EDIT : Nevermind, I just installed it, as later I can just uninstall it with make uninstall .... Now I'm recreating all the prefixes ... I hope this works ...

They're very much not ready, or even functional, and I believe it's actually not a high priority. Don't quote me on that, though, as I can't remember the discussion I'm thinking of too well right now..._________________Kind Regards,
~ The Noob Unlimited ~