Some of us on wine-users are trying to get Wine to install on OpenBSD. First, of course, we need to get it to compile on OpenBSD ...
Are bugs on this platform considered valid reportable bugs? I couldn't find any OpenBSD bugs on a quick search in Bugzilla.
State of things: it doesn't compile cleanly yet, and ./configure seems to fail to recognise a lot of libs that are in fact present.
(I realise that running Windows on OpenBSD may cause a matter-antimatter explosion as the two security models meet ... But it has *hack value*!)
- d.
On Fri, Dec 26, 2008 at 2:16 PM, David Gerard dgerard@gmail.com wrote:
Some of us on wine-users are trying to get Wine to install on OpenBSD. First, of course, we need to get it to compile on OpenBSD ...
Are bugs on this platform considered valid reportable bugs? I couldn't find any OpenBSD bugs on a quick search in Bugzilla.
State of things: it doesn't compile cleanly yet, and ./configure seems to fail to recognise a lot of libs that are in fact present.
(I realise that running Windows on OpenBSD may cause a matter-antimatter explosion as the two security models meet ... But it has *hack value*!)
- d.
File bugs on compiling issues, if you're sure they're bugs in wine and not bugs in OpenBSD.
FWIW, I'm working on trying this, but installing it in VirtualBox gives segfaults galore. I'm going to try putting it on a spare HDD on bare metal and see if that works better.
2008/12/26 Austin English austinenglish@gmail.com:
On Fri, Dec 26, 2008 at 2:16 PM, David Gerard dgerard@gmail.com wrote:
Some of us on wine-users are trying to get Wine to install on OpenBSD. First, of course, we need to get it to compile on OpenBSD ... Are bugs on this platform considered valid reportable bugs? I couldn't find any OpenBSD bugs on a quick search in Bugzilla. State of things: it doesn't compile cleanly yet, and ./configure seems to fail to recognise a lot of libs that are in fact present.
File bugs on compiling issues, if you're sure they're bugs in wine and not bugs in OpenBSD.
When OpenBSD refuses to put up with a dodgy virtual machine, they regard that as a feature rather than a bug ;-)
OpenBSD basically doesn't work properly in a lot of VMs because it is serious about not letting programs misbehave in ways that could cause insecurities. So stuff you can get away with on Windows and even Linux breaks it.
FWIW, I'm working on trying this, but installing it in VirtualBox gives segfaults galore. I'm going to try putting it on a spare HDD on bare metal and see if that works better.
In the case of VirtualBox, OpenBSD not working has been acknowledged by the VirtualBox developers as "known bug, our emulation's imperfect, no paying customers affected, go away." So don't expect it to work in the foreseeable future unless you have a large Sun contract and they ask why you went with VMware.
I'm currently playing with it in QEMU - don't try this with kqemu, that's known to break OpenBSD too! - and reliably geting the ENOTSUP compile-time error (which I'm about to file a bug on). I'll be getting a spare dual AMD64 next week to try it on OpenBSD under 32-bit and 64-bit.
I looked in Bugzilla again and saw a few filed bugs ... I'll see if I can reproduce the "abandoned" ones on current Wine tarballs. More to come! %-D
- d.
Austin English wrote:
On Fri, Dec 26, 2008 at 2:16 PM, David Gerard dgerard@gmail.com wrote:
Some of us on wine-users are trying to get Wine to install on OpenBSD. First, of course, we need to get it to compile on OpenBSD ...
Are bugs on this platform considered valid reportable bugs? I couldn't find any OpenBSD bugs on a quick search in Bugzilla.
State of things: it doesn't compile cleanly yet, and ./configure seems to fail to recognise a lot of libs that are in fact present.
(I realise that running Windows on OpenBSD may cause a matter-antimatter explosion as the two security models meet ... But it has *hack value*!)
- d.
File bugs on compiling issues, if you're sure they're bugs in wine and not bugs in OpenBSD.
FWIW, I'm working on trying this, but installing it in VirtualBox gives segfaults galore. I'm going to try putting it on a spare HDD on bare metal and see if that works better.
David:
File a bug when you think it is Wine related as it pertains to the ability to build on that platform.
Austin:
OpenBSD does not like virualization of any kind. VMWare does not support it, from what I remember.
James McKenzie
2008/12/27 James McKenzie jjmckenzie51@earthlink.net:
David: File a bug when you think it is Wine related as it pertains to the ability to build on that platform. Austin: OpenBSD does not like virualization of any kind. VMWare does not support it, from what I remember.
Yep. In the present case, I'll hold off filing any bugs (e.g. the ENOTSUP compile error - if you try compiling Wine on OpenBSD you *will* get this) until I've done them on a real physical PC. Though QEMU on my laptop is good enough for my present pottering about.
- d.
On Friday 26 December 2008 21:16:58 David Gerard wrote:
Some of us on wine-users are trying to get Wine to install on OpenBSD. First, of course, we need to get it to compile on OpenBSD ...
Are bugs on this platform considered valid reportable bugs? I couldn't find any OpenBSD bugs on a quick search in Bugzilla.
They are considered valid bugs, but be prepared to go through a lot of iterations if developers aren't able to test on their own machines. (At least I don't have a spare just for toying with OpenBSD) Basically, the best way to get a new, uncommon POSIX OS supported in Wine is to get somebody familiar with (programming on) the OS to work on Wine, or at least closely with the Wine developers. That's how FreeBSD was fixed to better support Wine's needs some time ago. This required a couple of patches to the FreeBSD kernel, IIRC, so if the OpenBSD kernel lacks a feature Wine needs, you might have to spend time talking to the OpenBSD team to get features added.
Cheers, Kai
-
Austin English -
David Gerard -
James McKenzie -
Kai Blin