What happens when you give Wine to a GNU Hurd?

/!\ Pages in CategoryDistributions aren't intended to be permanent. Wine has only become stable on the Hurd recently (summer 2015) so keep this page for now. In the future though, consider moving any relevant info to a static page on WineHQ and deleting this one.

{i} The Hurd actually isn't a complete environment but a distinct kernel (like the Linux, System V, and BSD kernels). The Hurd has been in development on-and-off for over 30 years, and is based on the CMU Mach microkernel. It consists of only a microkernel and userspace components (that handle functions otherwise included in a monolithic kernel). As a result, unless you're actually developing patches for Wine to run on the Hurd, you probably need to worry more about the environment you're using.

(!) Currently, the Debian Hurd port is the most stable and popular so you might want to see the Debian page for info on installing and building wine.


{i} Wine 1.7.28 should run well on Debian GNU/Hurd 2013. Debian GNU/Hurd 2015 is out too now so that should makes two releases of Debian Hurd that play well with a Wine development release!

<!> Unfortunately, Wine 1.6 still won't run on GNU/Hurd, though AndreHentschel's MAX_PATH patches should fix the last problems. Hurd support wasn't a high enough priority to justify patching the stable branch, but with Wine 1.8, there should finally be a stable Wine release that can run with the Hurd.

<!> There was previously an issue with old versions of eglibc (prior to 2.17-94), but with the merge of eglibc into glibc and the 2015 release of Debian GNU/Hurd, you probably don't need to worry about it.

Hurd-related Wine patches:

See also


Hurd (last edited 2015-08-12 08:25:48 by KyleAuble)