Created attachment 433548 [details] Output of emerge --info sys-devel/llvm sys-devel/llvm-3.5.0 builds successfully, however at the end I get the following message, despite I'm not a 'hardened' user: * Messages for package sys-devel/llvm-3.5.0: * Failed to set XATTR_PAX markings -me Release/bin/llvm-rtdyld. * Failed to set XATTR_PAX markings -me Release/bin/lli. * Failed to set XATTR_PAX markings -me Release/bin/lli-child-target. Even if this behavior is normal, it may confuse other users.
Gentoo is not hand holding distro. if you cannot use Google for a fairly distinctive message (that doesn't even affect anything), consider using a different distro. for technical reasons the warning cannot be removed without causing other issues.
(In reply to Alex Xu (Hello71) from comment #1) > Gentoo is not hand holding distro. if you cannot use Google for a fairly > distinctive message (that doesn't even affect anything), consider using a > different distro. > > for technical reasons the warning cannot be removed without causing other > issues. I believe, and many would agree with me, that error and warning messages produced by such a critical system component as package manager, are not something to be ignored, even if they allegedly do not affect anything. Moreover, the practice of repeatedly displaying meaningless warning messages to user usually causes the user to develop a bad habit to treat them lightly, and eventually they will miss a meaningful one. If there is no easy fix, then, I think, this is a good reason to discuss possible solutions or, at very least, make a clear comment in the Handbook. As a side note, would you please be so kind to refrain from giving anyone advice on what software to use based on unjustified perception of that person's ability to google? Another note, which I should have included in the bug report: my PORTAGE_TMPDIR is on ext4 and the kernel is compiled with CONFIG_EXT4_FS_SECURITY=y.
(In reply to Nikolay Belikov from comment #2) > Another note, which I should have included in the bug report: my > PORTAGE_TMPDIR is on ext4 and the kernel is compiled with > CONFIG_EXT4_FS_SECURITY=y. we patch the gentoo-sources and hardened-sources kernels such that user.pax.flags namespace is enabled on tmpfs. this is needed whether or not you use hardened gentoo because we have some users which will switch between hardened + non-hardened kernels and can't afford to have their system break because of missing pax flags. also, this is not an upstremable patch, you won't get it in vanilla-sources or other kernel flavors. finally, tracing the xattrs from filesystem to filesystem as things gets copied around would be a lot of work for little gain. i'm willing to accept patches, but otherwise, its pretty corner case, and i am going with WONTFIX.
(In reply to Anthony Basile from comment #3) > (In reply to Nikolay Belikov from comment #2) > > > Another note, which I should have included in the bug report: my > > PORTAGE_TMPDIR is on ext4 and the kernel is compiled with > > CONFIG_EXT4_FS_SECURITY=y. > > we patch the gentoo-sources and hardened-sources kernels such that > user.pax.flags namespace is enabled on tmpfs. this is needed whether or not > you use hardened gentoo because we have some users which will switch between > hardened + non-hardened kernels and can't afford to have their system break > because of missing pax flags. also, this is not an upstremable patch, you > won't get it in vanilla-sources or other kernel flavors. finally, tracing > the xattrs from filesystem to filesystem as things gets copied around would > be a lot of work for little gain. I'm sorry, but due to my limited understanding of how extended attributes work and how emerge deals with them, I cannot correlate your answer with my comment. To make it clear, I added a note about the filesystem and kernel flags, because when I searched for similar problem reports, I've found that this issue arises when PORTAGE_TMPDIR is moved to tmpfs (which I didn't do), and the solution was to ensure that the kernel has the required flags (which I already have set).
nope, I'm definitely not part of this. take it up with hardened project if you want.
Hardened is not supported anymore.
