Details of app-emulation/wine-staging:

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks

GCC-5.0-5.3 suffered from compiler bugs and are no longer supported by
Gentoo's Toolchain Team. If your ebuild fails the compiler checks in
the configure phase, either update your compiler or switch to <5.0 || >=5.4
Compilation can hang with CFLAGS=\
around this by adding \
See package.env in man 5 portage for more information on how to do this.
See https://bugs.gentoo.org/show_bug.cgi?id=613128 for more details
Applying the Wine-Staging patchset. Any bug reports to the
Wine bugzilla should explicitly state that staging was used.
Skipping tests since they cannot be run under the root user.
To run the test ${MY_PN} suite, add userpriv to FEATURES in make.conf
Without Wine Gecko, wine prefixes will not have a default
implementation of iexplore.  Many older windows applications
rely upon the existence of an iexplore implementation, so
you will likely need to install an external one, like via winetricks
Without Wine Mono, wine prefixes will not have a default
implementation of .NET.  Many windows applications rely upon
the existence of a .NET implementation, so you will likely need
to install an external one, like via winetricks