| View previous topic :: View next topic |
| Author |
Message |
cwc
Veteran
Joined: 20 Mar 2006
Posts: 1281
Location: Tri-Cities, WA USA
|
 Posted: Sat Apr 06, 2013 1:14 pm Post subject: Two errors in last update: XATTR_PAX ? [solved] |
 |
|
Here's my emerge world: emerge -DuNva world
I got a few errors I'm not sure of.
Any ideas?
Here are the XATTR flags in my .config file:
azzerare linux-3.7.10-gentoo # grep XATTR .config
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_TMPFS_XATTR=y
# CONFIG_CIFS_XATTR is not set
azzerare linux-3.7.10-gentoo #
| Code: |
* Messages for package net-fs/cifs-utils-5.9-r1:
* setuid use flag was dropped due to multiple security implications
* such as CVE-2009-2948, CVE-2011-3585 and CVE-2012-1586
* You are free to set setuid flags by yourself
* Messages for package dev-lang/v8-3.16.14.9-r1:
* Failed to set XATTR_PAX markings -me for:
* out/x64.release/mksnapshot
* Executables may be killed by PaX kernels.
* Failed to set XATTR_PAX markings -me for:
* out/x64.release/shell
* Executables may be killed by PaX kernels.
* Messages for package www-client/chromium-26.0.1410.43:
* bindist enabled: H.264 video support will be disabled.
* Failed to set XATTR_PAX markings -me for:
* out/Release/chrome
* Executables may be killed by PaX kernels.
*
* Messages for package www-client/opera-12.15_p1748:
* Failed to set XATTR_PAX markings -me for:
* /var/tmp/portage/www-client/opera-12.15_p1748/image///usr/lib64/opera/opera
* Executables may be killed by PaX kernels.
>>> Auto-cleaning packages...
|
_________________
Without diversity there can be no evolution:)
Last edited by cwc on Tue May 21, 2013 11:44 am; edited 1 time in total |
|
| Back to top |
|
 |
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Sat Apr 06, 2013 11:02 pm Post subject: |
|
|
I believe it may be fixed already. Give it time for the fix to propagate through the mirrors, re-sync and retry.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
| Back to top |
|
|
floppymaster
Developer
Joined: 07 Jul 2010
Posts: 229
Location: Detroit, MI, USA
|
| Posted: Sat Apr 06, 2013 11:13 pm Post subject: |
|
|
| Those should just be warnings (non-fatal). They are typical if you have PORTAGE_TMPDIR on a tmpfs. tmpfs does not support user extended attributes, which are required for the XATTR_PAX markings. |
|
| Back to top |
|
|
cwc
Veteran
Joined: 20 Mar 2006
Posts: 1281
Location: Tri-Cities, WA USA
|
| Posted: Sun Apr 07, 2013 12:42 am Post subject: |
|
|
| floppymaster wrote: | | Those should just be warnings (non-fatal). They are typical if you have PORTAGE_TMPDIR on a tmpfs. tmpfs does not support user extended attributes, which are required for the XATTR_PAX markings. |
Thanks for the reply. What exactly is PORTAGE_TMPDIR on a tmpfs and where is it set?
_________________
Without diversity there can be no evolution:) |
|
| Back to top |
|
|
floppymaster
Developer
Joined: 07 Jul 2010
Posts: 229
Location: Detroit, MI, USA
|
| Posted: Sun Apr 07, 2013 1:10 am Post subject: |
|
|
PORTAGE_TMPDIR is set in make.conf; it defaults to /var/tmp.
tmpfs is a type of filesystem that lives in memory. If you don't know what it is, chances are you are not using it for /var/tmp.
In any case, if you aren't using a hardened (PaX) kernel, the warnings don't matter. |
|
| Back to top |
|
|
|
Portage & Programming
