Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 236137 - A possible ebuild patch for app-emulation/wine for PAX enabled systems
Summary: A possible ebuild patch for app-emulation/wine for PAX enabled systems
Status: RESOLVED DUPLICATE of bug 164814
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High enhancement (vote)
Assignee: Wine Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-29 17:38 UTC by James Browning
Modified: 2008-08-30 03:15 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
A patch to the ebuild for app-emulation/wine (wine.patch,1.12 KB, patch)
2008-08-29 17:44 UTC, James Browning
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description James Browning 2008-08-29 17:38:14 UTC
An ebuild patch to enable recent versions of wine to run without further modification on systems with mprotect from PAX enabled.

Reproducible: Always

Steps to Reproduce:
1. Emerge wine on a pax system w/ mprotect
2. try to run wine

Actual Results:  
wine is killed by the kernel mprotect feature for trying to execute in anonymous memory

Expected Results:  
wine should run without trouble

I had a version this working on a 1.1.2 ebuild modified from the stock 1.1.0 ebuild. I can't get 1.1.3 to build, but that is a different issue.
Comment 1 James Browning 2008-08-29 17:44:34 UTC
Created attachment 164071 [details, diff]
A patch to the ebuild for app-emulation/wine

this should enable wine to run on hardened systems without modification, however it is not production ready I think, in that there are likely apps that would remain broken.
Comment 2 SpanKY gentoo-dev 2008-08-30 03:14:19 UTC
Comment on attachment 164071 [details, diff]
A patch to the ebuild for app-emulation/wine

not the way to go ... find the real issue and address it
Comment 3 SpanKY gentoo-dev 2008-08-30 03:15:15 UTC

*** This bug has been marked as a duplicate of bug 164814 ***