This is probably an upstream bug that I'd like to track also here because of bug 607990. We know that a proper config should have one of CONFIG_PAX_PT_PAX_FLAGS/CONFIG_PAX_XATTR_PAX_FLAGS but the actual autoconfig picks both. This may lead to failure like what we have in bug 607990.
blueness has told me that CONFIG_PAX_PT_PAX_FLAGS is on its death bed. It should probably just pick CONFIG_PAX_XATTR_PAX_FLAGS now.
(In reply to James Le Cuirot from comment #1) > blueness has told me that CONFIG_PAX_PT_PAX_FLAGS is on its death bed. It > should probably just pick CONFIG_PAX_XATTR_PAX_FLAGS now. correct, i didn't want to hard force these on or off for backwards compatibility, so i just chose a default setting which was congruent with what we are supporting going forward.
Any progress here? Please note that enabling both CONFIG_PAX_PT_PAX_FLAGS and CONFIG_PAX_XATTR_PAX_FLAGS breaks the build system of app-editors/emacs:25. (However, I'll close any Emacs bug about this issue as invalid, because everyone keeps telling me that this is not a supported kernel configuration.)
