| 1 |
Hi! |
| 2 |
|
| 3 |
On Sun, Jun 08, 2014 at 10:31:58AM +0200, "Tóth Attila" wrote: |
| 4 |
> > When running with a pax kernel, you must enable EMUTRAMP in your Kconfig |
| 5 |
> > and you must paxmark your python exe's with E. Note: EMUTRAMP is on by |
| 6 |
> > default and the ebuild automatically does the markings for you, so leave |
| 7 |
> > the defaults alone. |
| 8 |
|
| 9 |
Enabling EMUTRAMP fixed this issue, thanks! |
| 10 |
|
| 11 |
> I see a problem here, that Alex has python binaries installed on his |
| 12 |
> system with inconsistent PAX markings (PT: e, XATTR: E). I don't know his |
| 13 |
|
| 14 |
I've disabled support for PT in kernel, so only XATTR value works and this |
| 15 |
inconsistency isn't important. But, anyway, I wonder why after re-emerging |
| 16 |
python it has this inconsistency in flags? (I've just run paxctl-ng -f and |
| 17 |
it works - set PT flag to "E" instead of "e".) |
| 18 |
|
| 19 |
-- |
| 20 |
WBR, Alex. |
Archives