Re: Building Wine on amd64 FreeBSD?
On 05-07-2012 23:37, Hilko Bengen wrote: Following Marcus Meissner's advice how to build a WoW64 setup (thanks!), I have succeeded in building a set of co-installable i386/amd64 Debian packages. Those won't make it into the wheezy release as I was just a bit late for the freeze, but I have uploaded packages to experimental. What didn't work was building the 64-bits of wine on Debian/kfreebsd-amd64 (Debian userland including GNU libc on a FreeBSD kernel): https://buildd.debian.org/status/fetch.php%3Fpkg%3Dwine%26arch%3Dkfreebsd-amd64%26ver%3D1.4.1-1.2%26stamp%3D1341358832 Apparently the reason is that the uc_mcontext structure does not store the DS, ES, FS, and GS registers. After I made the changes below, everything compiled, but how useful is the result? Are those registers contained in uc_mcontext on plain FreeBSD? They were added in FreeBSD 8: http://svnweb.freebsd.org/base/head/sys/amd64/include/ucontext.h
Re: winebuild port to ARM?
Am 18.04.2012 00:16, schrieb André Hentschel: Am 17.04.2012 03:09, schrieb Roger Cruz: Hi Andre, I am willing to help as much as my knowledge allows me to port this. The last time I wrote anything in ARM was about 15+ years ago so my knowledge of it is rather limited. I'm also trying to understand what every line of the assembly code is doing in x86. If someone with more knowledge were willing to port this file for us, it would be a great start :-) but failing that, I can fold up my sleeves and take a crack at it. First: Please bottom post on this list. I doubt someone else will port it anytime soon, so maybe you start trying it and i try to help you as much as i can or you wait until i get time to do it myself. It seems we were misreading the source. winebuilds relay.c has nothing to do with relay tracing. the code is in ntdlls relay.c and in winebuilds spec32.c in function output_relay_debug. I'm working on it as it's much easier than what i've seen in the wrong file :) Expect a patch quite soon. -- Best Regards, André Hentschel
Re: Policy for the Wiki?
On Wed, Jul 4, 2012 at 4:16 PM, Kyle Auble randomidma...@yahoo.com wrote: Hello all, I've been working on the wiki recently and noticed that a lot of out-of-date or redundant information is retained. For example, completed tasks on to-do lists are checked off and never removed. Isthere an unofficial policy of not deleting info, even if it may exist elsewhere (in the git repo history, wikipage revision history, etc)? Other instances might be stubs dedicated to features in development years ago, or pages on bugs that have already been fixed or triaged in Bugzilla.I know even page deletions can still be reverted, but I wanted to check first before cleaning things out more aggressively. If there are a few unwritten rules everyone likes the wiki to follow, I could add them somewhere as editing guidelines. The wiki tends to have some bit rot, and if you're willing to keep it clean, then I'd say you get more leeway in the editing guidelines. In general though, yes, old info should be updated/removed. Old taskslists, it's a bit more dependent. For instance, the 1.0 / 1.2 / 1.4 task lists are probably useful for old reference, but others could possibly go (may need some examples though). While the topic's up, I was also wondering how moinmoin was chosen as the wiki engine. I couldn't really find a discussion on the mailing lists so I figured it was the best option when the wiki was first started. I can appreciate that it doesn't require a database and it's written in python instead of php. Allowing only inline CSS in tables causes some headaches, but mainly it can be really slow sometimes, especially when editing, and unless using wikilinks or going directly to a page, navigation is tricky. Has the possibility of migrating the wiki to a different engine ever come up? Or does the Wine wiki code just need some tweaking and maybe some tools? To be honest, I don't know if there is a better alternative (MediaWiki is designed for a very different use case and has really messy code). It just seems like something is discouraging even basic upkeep on the wiki, which kind of defeats its whole purpose. -Kyle Dimi Paun (CC'ed) set up/runs the wiki, so he'd be the guy to ask. Other people have discussed MoinMoin/alternatives before, but to my knowledge, there hasn't been much effort put into changing it. -- -Austin
Debugging wine/windows applications
I tried to run wine under gdb and failed. Using multiprocess gdb I endup with weird trace: 0xf7ffd430 0x7bc846f9 0x7bc8480f 0x7bc84855 0x7bc42a94 0x7bc433b1 0x7b8772f7 0x7ebab89b 0x7bc80014 0x7bc8005d Where 0x7** addresses are not connected to any module. And 0xf** addresses are from /lib/ld-linux.so.2, debug symbols for which I can't find. Can somebody explain what's hapenning? Running wine with winedbg under gdb fails with message err:module:LdrInitializeThunk Main exe initialization for LC:\\windows\\system32\\notepad.exe failed, status c022 Is there any tutorial on how to run wine with applications under gdb?
Re: Policy for the Wiki?
On Friday, July 6, 2012 at 3:14 PM, Austin English wrote: Dimi Paun (CC'ed) set up/runs the wiki, so he'd be the guy to ask. Other people have discussed MoinMoin/alternatives before, but to my knowledge, there hasn't been much effort put into changing it. Thanks for the suggestion. I've looked into the moinmoin code a little more, and Dimi already switched out the cgi module. Besides possibly updating to a newer version and adding Xapian search, there may not be much more that can be done on the software end. Ubuntu wiki is fast and it apparently uses moinmoin so it could just be server resources too. If that's the case then moinmoin is probably still the best choice: uses python, no database required, customizable, and it seems to be the main alternative to MediaWiki. On a side note, is there any talk of moving the wiki code from the sourceforge CVS repo to a Git one at WineHQ someday? -Kyle P.S. Sorry about the word-wrapping in my last email. Yahoo zigged when I thought it would zag.
