From WineHQ Wiki
Revision as of 10:30, 24 January 2016 by AndreHentschel (talk | contribs) (Initial import)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


What happens when you give Wine to a GNU Hurd?

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.


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!

Dialog-warning.svg 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